There are a number of reasons you might need to remove the wheel arch liner/splashback. On the Corsa, you need to remove part of it in order to gain access to the screenwash bottle and the horn.

They do sometimes get damaged too - if the rear portion develops a split or a hole, you'll want to replace it to reduce the risk of road water getting sprayed all over your sills.

This documentation details how to remove and refit the Front Wheel Arch Liner on a Vauxhall Corsa E - it's demonstrated on a 2015 model, but the procedure should be the same across all model years.

Read more…

It's not often that you need to remove or replace a screenwash bottle, however they do sometimes get damaged or develop leaks.

The first stages of this process can also be used in order to gain access to the screen wash motor/pump (Vauxhall part number 13349273) and the horn (Vauxhall part number 13489938) if either of those is in need of replacement.

This documentation provides details on how to access, remove and replace the screenwash reservoir (Vauxhall part number 13432705) on a Vauxhall/Opel Corsa (Mk 4) E, and should apply to model years 2014-2019.

Read more…

Replacing a foglamp unit on a Vauxhall (Opel) Corsa Mk4 (E) is relatively straight forward. This procedure should work on all years between 2014 and 2019. This procedure will also allow you to replace the foglight surround trim if needed.

Read more…

There a variety of reasons you may need to remove the bumper on a Vauxhall Corsa, including bumper replacement, gaining access to the screenwash reservoir or foglight unit replacement.

The procedure is fairly straightforward and isn't that dissimilar to that followed when replacing headlights bulbs on a Corsa D.

This documentation details how to remove and re-install the front bumper on a Vauxhall (or Opel) Corsa E (also known as a Corsa Mk4). The images show a 2015 Corsa E, but the same process should apply for model years 2014 to 2019.

Read more…

It's increasingly impossible to avoid the hype around Web3 and depending on who you speak to it's going to deliver different things

1. Easier monetization by content creators
2. Improved privacy
3. Decentralisation: Removal of the centralisation onto gatekeepers/platforms that occurred with Web 2.0
4. A trustless, self-governing model

I find that Web3 presents an interesting conflict within me. I've long identified with many of the ideals held by Cypherpunks, including building anonymous tools to defend privacy. One of the tools explicitly called out, even back in 1993 when the Cypherpunk's Manifesto was written, is crypto currency

We the Cypherpunks are dedicated to building anonymous systems. We are defending our privacy with cryptography, with anonymous mail forwarding systems, with digital signatures, and with electronic money.

On the face of it, I should support Cryptocurrency and Web3 and yet, I just don't buy it.

I've had discussions about Web3 on Reddit as well as various forums lately, and of course, there's the recent fantastic analysis by Moxie Marlinspike.

I thought it might be helpful (to me) to put some of those thoughts into some sort of order. This post is going to explore some of the claims around Web3 and the issues I see with them.

Read more…

It's possible, on Linux, to have multiple swap partitions and/or swapfiles so that your swapspace is spread across multiple physical devices.

It's also sometimes desirable to set an order of priority for these, so that paging uses the fastest underlying storage first.

This documentation details how to set up a mix of swap files and partitions and tell the kernel how to prioritise it's swapsources Linux.

Read more…

Running a Minecraft server has always been fairly painless, with the biggest headache usually being getting the right version of Java up and running.

I wanted to find an even simpler route, though, and wanted something that gave me the ability to monitor the server (if only so I could fix stuff before getting complained at).

Although I came into this ready to build my own images, it turns out a bloke called Geoff has done a sterling job not only of dockerising Minecraft-server, but also creating a monitoring tool.

This documentation details how to tie that all together in order to use Docker to stand up a Minecraft Java edition server and monitor it using Telegraf to push monitoring data into InfluxDB or InfluxCloud. Technically, this should all work with running a Bedrock server too, but I've not tried that.

This document assumes you're running Ubuntu, but if you're not then it's only really the Docker installs steps which are Ubuntu specific.

Read more…

In April 2016, I got bored and created a second crypto trail on www.bentasker.co.uk. Unlike the first this trail wasn't confined to a single domain, or even to just the clearnet.

However, in order to follow the trail, you needed to be able to access a site served using a V2 Onion. However, V2 onions have since been deprecated and are no longer accessible.

The trail is now broken.

But, it is still possible to complete the challenges, so this post will begin by presenting the challenge and then will provide the solution.

Read more…

My recent migration from Joomla! to Nikola has come at the cost of partially breaking one of the cryptotrails hidden in the original site.

I first added this cryptotrail into www.bentasker.co.uk in August 2014.

The trail was designed to test across a range of skills that all self-respecting hackers should work to develop - not just technical knowledge, but observation and fact-finding skills.

This post details how the trail could be followed, and how to resolve each step of it.

Read more…

I launched mailarchives.bentasker.co.uk back in 2014. As well as hosting mirrors of mailing lists such as tor-talk and cypherpunks, it also hosted mail based notifications derived from multiple sources (such as RSS feeds, lists etc) like my CVEs list.

However, I've taken the decision to take mailarchives.bentasker.co.uk offline - this post details the rationale behind that choice.

Read more…