tl;dr on how to implement this?
If you want to be harder to fingerprint in Firefox, use LibreWolf.
I do wonder whether Firefox can now do this without severely restricting website functionality, though. Leaving on fingerprint resistance in LibreWolf hobbles many sites.
I tried it for like half an hour. 15 minutes of which i spent on capchas. It is unusable on a lot of the Internet
I’m using a VPN and Vanadium and do I get captchas a lot; it’s mostly a mild annoyance though. The times I can’t get through at all are rare, but more often it’s that I decided the content is not woth the wait.
What does your browser identify as when you run a fingerprint test? Because if it still claims youre running Firefox or librewolf, that is basically all the fingerprint they need to get you. The ff/lw market share is basically a fingerprint of its own.
edit: Tested Librewolf, fresh install, but turned up all the anti-fingerprinting stuff got uniquely fingerprinted by https://amiunique.org/ . I dont know what the anti-fingerprinting stuff does, but its not even close to enough.
I guess Whonix VM and Mullvad browser with it’s VPN are the only working anti-fingerprinting tools so far. It’s genuinely that difficult to get anti-fingerprinting right, because there are like a bazillion ways to get fingerprinted.
And personally I just stopped bothering with anti-fingerprinting because of this. I think I did my fair share of hurting the mass surveillance machine by getting a few contacts to Signal, occasionally using AdNauseum, and donating a bit to Graphene OS. Might as well let myself be fingerprinted now.
$ sudo apt install librewolf [sudo: authenticate] Password: Error: Unable to locate package librewolfStill waiting for it to show up in the official Debian (or Ubuntu) repositories. I’m aware that they publish to their own repository that they recommend adding to your system, but I don’t want to taint my install like that.
Use a flatpak
Of course there are other ways I could install it, but that’s beside the point. Normal Free Software belongs in distros’ package repositories.
That means you expect the software to have a manteiner for every single distro, each with their own hurdles.
That’s exactly the point flatpaks and appimages are solving, and how it seems things are going moving forward.
They also provide
- an extra level of sandboxing/isolation for security
- isolation of the package’s dependencies from your base OS for stability
Not for all software, but for many office/productivity/internet tools, I ❤️ flatpak
I agree, while they aren’t perfect, using apps like FlatSeal to toggle and remove permissions for Flatpak apps is a lot easier than writing firejail or brwap configs for standard apps.
You could spin up an Arch or Fedora distrobox, install it in that, and then create link for it to your host system (easily done with a gui app like BoxBuddy if you’re allergic to CLI). No noticable overhead.
I think there’s a flatpak too?
