I’ve just been playing around with https://browserleaks.com/fonts . It seems no web browser provides adequate protection for this method of fingerprinting – in both brave and librewolf the tool detects rather unique fonts that I have installed on my system, such as “IBM Plex” and “UD Digi Kyokasho” – almost certainly a unique fingerprint. Tor browser does slightly better as it does not divulge these “weird” fonts. However, it still reveals that the google Noto fonts are installed, which is by far not universal – on a different machine, where no Noto fonts are installed, the tool does not report them.
For extra context: I’ve tested under Linux with native tor browser and flatpak’d Brave and Librewolf.
What can we do to protect ourselves from this method of fingerprinting? And why are all of these privacy-focused browsers vulnerable to it? Is work being done to mitigate this?
Disable javascript, trying to get around fingerprinting with javascript enabled is an exercise in futility, and is especially risky with something as heavily monitored as tor.
Disable javascript, trying to get around fingerprinting with javascript enabled is an exercise in futility, and is especially risky with something as heavily monitored as tor.
I like disabling JS myself for some web browsing but this can make fingerprinting easier because most people do enable JS, and I’ve read that with JS disabled certain things still can be detected through CSS files.
I feel like on Tor specifically, disabled JS is far more common than on clearnet connections so not as big of an issue.
Disable javascript
This is like those people who say that the only form of safe sex is abstinence. Technically true, practically useless.
I’m slowly starting to agree with @ssm that safeguarding against fingerprinting is an exercise in futility though…QubesOS sounds like something that might help though, since it makes it easy to browse from a virtual machine with fonts and other settings that may be leaked set to the most bog-standard defaults.
On a related note, disabling javascript can actually improve your user experience quite a lot for certain types of tasks. A lot of news/blogs/article-style websites nowadays are actually more usable without javascript, because you don’t have to waste time closing all of the ads and cookie popups. I have a separate browser profile with js disabled and use it quite a lot.
No script lets you individually allow js on certain sites, even specific sources. Block all by default, allow safe sites or temporarily allow other sites based on need. I started doing that this year and it hasn’t been nearly as much trouble as I thought it would be.
Tor has noscript automatically enabled no?
Tor has noscript automatically enabled no?
There’s three security settings via NoScript in Tor browser. The default has JS enabled.
It should, but I guess this user disabled it. I visited the same site with javascript disabled and it can’t fingerprint it (not in tor browser, I don’t trust it (css has nasty fingerprinting capabilities, huge mozilla codebase), I use w3m with torsocks and my useragent set to tor browsers, also tested qutebrowser with js disabled).
IIRC, it actually goes deeper than just reporting what fonts are installed. Even if the font names and metrics are masked by the browser, scripts can render them to a canvas and sample the resulting pixels.
This is why I don’t install any custom fonts where a web browser can use them, and part of why I keep javascript disabled by default.
Out of curiosity, how much of the internet is unusable with js disabled? As in, how often do you run into sites that are essentially non-functional without?
how much of the internet is unusable with js disabled
Quite a lot actually. A lot of articles / blogs / news sites are actually more usable without javascript than with, because none of the annoying popups and shit can load. I suggest having two browser profiles: one with javascript enabled by default, and one with javascript disabled. So for things like online shopping, you’d open the js profile. And for things where you expect to do a lot of reading, use the nojs profile. Ublock origin also lets you temporarily enable/disable js for a particular website pretty easily.
I haven’t taken measurements, but there are many problematic sites these days. Lots of web developers fail to see the problems that javascript imposes on users, so they build web apps even when they’re serving static content, where a regular web site (perhaps with javascript enhancements that aren’t mandatory) would do just fine.
I selectively enable first-party scripts on a handful of sites that I regularly use and mostly trust (or at least tolerate). Many others can be read without scripts using Firefox Reader View. I generally ignore the rest, and look elsewhere for whatever information I’m after.
I wonder if running it in a container such as flatpak would help.
Flatpak is not a container and should not be thought of as such for security/privacy purposes:
In general though we try to avoid using the term container when speaking about Flatpak as it tends to cause comparisons with Docker and rkt, comparisons which quickly stop making technical sense due to the very different problem spaces these technologies try to address. And thus we prefer using the term sandboxing.
https://flatpak.org/faq/#Is_Flatpak_a_container_technology_
It can provide container-like functions if specifically configured for that, but that’s not normal and it shouldn’t be relied on as a security barrier.
There’s a summary here with some Tor browser findings : https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/18097#note_2961761
OK, my fingerprint for Tor Browser is 0b8c195e60af3e2c29ebb8adecb340b1. Is it so unique? What is yours?