Browser Hardening, Privacy, Anti-Fingerprint and Anti-Telemetry Guide

Turns out reader view is pretty nice! Simply using reader view can bypass a couple annoyances. Native and no plugin required.

Regular non-reader view = popup :frowning:

Summary

This is hilarious popup btw. “we care about your privacy”
so we are going to:

  • use precise geolocation data
  • actively scan device characteristics for identification
  • share it with 756 partners

To be clear I am not complaining that they are trying to use ads, that’s fine. I’m not even trying to pick on this website in particular. I am merely pointing out the contradiction of saying “we care about your privacy” and then in the very next paragraph describing all the ways in which they will violate your privacy.

A website has every right so serve me an ad. And I have every right to disallow or mitigate the mechanisms used to “actively scan device characteristics for identification”.

My device characteristics such as my location, canvas properties and current battery level, etc… is simply non ya biz.. This is why I refuse to accept these popups, even tho I’m blocking cookies so it doesn’t really matter if I accept.

You can serve me the ad, but you don’t get spy on me and sell my data to all your friends. It not even about the ads anymore, it’s the principal of the matter. You can’t have my data unless I explicitly allow you to.

No means no.

Reader view = no popup! :slight_smile:


I may be using reader mode more often… It feels like an objectively better user experience!

4 Likes

I’m slightly late to this news.

For Brave users: ‘strict’ fingerprinting mode has been removed:

As of chrome 122, there is a new switch to disable V8 optimizer, or whitelist/blacklist sites: Chrome Enterprise and Education release notes - Chrome browser - Chrome Enterprise and Education Help

chrome://settings/content/v8

brave://settings/content/v8

This is similar to Super Duper Secure Mode in Edge that disabled the JavaScript just-in-time (JIT) compiler to enable some extra security protections.

half of all vulnerabilities for the V8 JavaScript engine was related to the JIT process.
With the JIT engine turned off, it was possible for Edge to turn on protections – such as the hardware-based Control-flow Enforcement Technology (CET) from Intel, and Windows’ Arbitrary Code Guard (ACG) and Control Flow Guard (CFG) – that were previously incompatible with JIT.


To disable JIt / web asm for Firefox:

javascript.options.baselinejit = false
javascript.options.asmjs = false
javascript.options.ion = false
javascript.options.wasm = false

These are already disabled in TOR and Mullvad in Safer/Safest mode.

NOTE: restart required for changes to take effect!


Test WebAssembly features here:
https://wasm-feature-detect.surma.technology/

2 Likes

Couple days late on this one. Brave on android now requires Google Play Services library:

1 Like

TIL a new term: “Bounce Tracking”


Bounce tracking is a technique where a user clicks a link but ends up reaching their intended destination via an intermediary tracking page. This allows trackers to place and read ‘first-party cookies,’ which aren’t blocked by the browser, unlike third-party cookies.

For instance, imagine a user on flowers.example clicking a link to books.example. At the last moment, the tracker active on the former site reroutes the link through tracker.example. The user first lands on this tracking page, which then redirects them to books.example, enabling tracker.example to identify that the user is interested in both flowers and books.


An illustration depicting Bounce Through Tracking and Bounce Back Tracking
Photo credit: Google

If tracker.example manages to inject itself into the user’s browsing pattern frequently enough, it can build a detailed profile of the user. To combat this, Mozilla has announced a feature called ‘Bounce Tracking Protection,’ which will regularly cleanse Firefox of tracking data every 24 hours. The browser will utilize heuristic detection methods to identify and recognize bounce trackers.

https://privacycg.github.io/nav-tracking-mitigations/#bounce-tracking-mitigations

edit: google too

3 Likes

Don’t care for most LTT vids, but even the normies are getting fed up:

2 Likes

Good! That means I will only be a little strange in 5 years!

1 Like

Sadly those are still tech inclined people, normies think Google is “The Internet”, Samsung makes Chinese iPhones and have no idea tech tuber is even a thing.

1 Like

WebAssembly is pretty awesome. Why would you want to disable it?

Personally I think that is going a bit too far.

These settings are not recommendations. This is mainly to document the feature, as it would fall under the category of hardening. Users must evaluate settings as it applies to them.

If you read the linked article it will explain, but in short malicious WebAsm (or malicious data parsed by vulnerable WebAsm) can lead to arbitrary code execution (breaking out of the browser sandbox).

So from the linked article lets look at some of the mitigations:


It’s not common to run into these types of exploits in the day to day, but they do exist. These techniques are probably used more by advanced threat actors.

Disclaimer: I am not an expert.

2 Likes

sigh… perhaps I’m a fool for having hope.

My level1 prediction is that once google brings the hammer down with MV3, there will be a massive shift to Firefox or chromium forks that maintain MV2.

1 Like

updated OP with extensions notes from Arkenfox and will link again here:

thanks:

Chrome support for MV2 ending soon:


If you need any more reasons to leave chrome:

A system called “NavBoost” (cited by VP of Search, Pandu Nayak, in his DOJ case testimony) initially gathered data from Google’s Toolbar PageRank, and desire for more clickstream data served as the key motivation for creation of the Chrome browser (launched in 2008).

Chrome exists only to collect more clickstream data. You are the product (but you already knew that).

And some more details about the search algo:

See also:

2 Likes

A new challenger enters the arena!

Any one played around with ladybird yet?

3 Likes

Have not played around with it yet, but have set up a monthly donation for the project.

2 Likes

They are targeting their first alpha release for 2026, so it will be a while. To be honest, the whole thing is giving me a bit of fishy vibes, but I could be wrong.

based on what?

I haven’t looked into it too much yet. My interest in it comes from that it isn’t based on chromium or firefox engine. Guess we’ll see where it goes…

1 Like

I don’t know, some of their sponsorships are sort of weird…

Null, a publishing company comprised of 9 superstar team members and exactly one published game with 20 positive reviews on Steam. IDK, could be the GitHub guy’s passion project for all I know…

Then Shopify is paying for it. To have another browser engine to work the bugs out? If it’s for press or publicity or whatever they are doing a shit job.

Playbit is (developing) a fourth generation operating system. Coming in 2024.

Since yesterday, FUTO joined so they will put it up on their home page and Louis Rossmann might talk about it.

And most of all, I wish they had some sort of sustainable business model, because without one it will probably die because Chromium exists.

Oh, and they should probably pay some developer in India to redo their website, it’s horrendous and it’s not helping their cause.

2 Likes

Yep, FUTO did put it on their home page in grants section. Interesting, I can’t wait to see how this plays out.

2 Likes

In this weeks episode of Mozilla shenanigans…

it appears as of Firefox 128, you are opt-in by default to the new ad measurement feature: PPA (Privacy-Preserving Attribution)

In disbelief I just installed a fresh copy of stock FireFox 128.0-1 and…yup, there it is:

Sources copy pasta’d from video description:
2022 Blog Post: Privacy Preserving Attribution for Advertising
25 Page Explainer: Interoperable Private Attribution (IPA) Overview - Google Docs
Anonym Purchase: Mozilla Welcomes Anonym: Privacy Preserving Digital Advertising
Mailing List Update: https://groups.google.com/a/mozilla.org/g/dev-platform/c/D6GZiXW_Da8
User Blog: Privacy-Preserving Attribution | Firefox Help
Github Explainer: https://github.com/mozilla/explainers/tree/main/ppa-experiment
How It Works: Misconceptions about Firefox's Privacy Preserving Ad Measurement – Andrew Moore
CTO Response: Reddit - The heart of the internet


Quick Rant:

Summary

This should be off by default and user should have to opt-in.

Opt-out is a dark pattern.

This type of behavior is breaking trust on principal alone. I don’t care if the data is “anonymized” or “noisy aggregated”. To be clear, I am not opposed to more privacy respecting systems. But you must ask for consent before collecting more data and enabling this type of shit by default is not cool.

This is why your market share is dying mozilla. This type of behavior is why people are moving to Librewolf or chromium based browsers. This is not acceptable from a browser that claims to care about your privacy.

Mozilla: “At Mozilla, we believe that privacy is fundamental to a healthy internet.”

Then prove it.

/rant

2 Likes