3 ms·
I've been thinking for a while—what if the solution to fingerprinting wasn't making your browser less unique, but less constant? Take Canvas fingerprints. If y
by Wowfunhappy 6y ago
I've been thinking for a while—what if the solution to fingerprinting wasn't making your browser less unique, but less constant?
Take Canvas fingerprints. If you added a bit of randomness to how the browser renders pixels, the fingerprint would change each time you measured it. It would still be unique, but it would be a useless tracking tool.
Presumably I'm not the first person to come up with this, is there a reason it isn't done?
- antonok 6y agoThis is actually exactly what Brave does! Both for Canvas and WebAudio, which is also used for fingerprinting in a similar way. There's more info here if you're curious: https://brave.com/privacy-updates-4/ https://brave.com/privacy-updates-4/
- igravious 6y agoBut won't trackers start ignoring these cues? Here is Brave's take: https://brave.com/brave-fingerprinting-and-privacy-budgets/ https://brave.com/brave-fingerprinting-and-privacy-budgets/
- gtsop 6y agoThis deserves to be heard. I will also add to this, since it is known we can use addons to disable tracking and fingerprinting but addons can themselves be used for fingerprinting, why don't we get a feature on firefox (or even one more addon) to prevent javascript from getting a true result when querying for known addons?
- kdrag0n 6y agoBromite for Android does that: https://github.com/bromite/bromite/blob/73ef7f3ea1937f5ba8ebad2ca6b8cc345cfaa060/build/patches/Multiple-fingerprinting-mitigations.patch https://github.com/bromite/bromite/blob/73ef7f3ea1937f5ba8eb...
- surround 6y agoRandomizing fingerprints is generally a bad idea. See: https://github.com/arkenfox/user.js/wiki/4.1-Extensions#small_orange_diamond-%EF%B8%8F-anti-fingerprinting-extensions-fk-no https://github.com/arkenfox/user.js/wiki/4.1-Extensions#smal...
- Wowfunhappy 6y agoSorry, I don't actually see in there why randomizing something like a canvas or webaudio fingerprint is a bad idea. I believe they know what they're talking about, but I'd still like to know why. Notably, to me this isn't necessarily about beating the resistFingerprints setting, because I can't use that setting. For good or for ill, it breaks too much of the web.
- gruez 6y ago>Sorry, I don't actually see in there why randomizing something like a canvas or webaudio fingerprint is a bad idea Literally the first bullet >It is trivial to detect RFP and when you change a RFP metric, you lose your "herd immunity"
- Wowfunhappy 6y agoBut that's referring to privacy.resistFingerprinting (RFP), not adding randomness. RFP isn't really an option, at least for me, because it breaks too many sites.
- gruez 6y ago>But that's referring to privacy.resistFingerprinting (RFP), not adding randomness having a randomized fingerprint is a fingerprint value in and of itself. That may leak more entropy bits if you have a fairly common hardware configuration Also, regarding webaudio fingerprinting, afaik it's not a real threat. https://github.com/WebAudio/web-audio-api/pull/2224#discussion_r457167513 https://github.com/WebAudio/web-audio-api/pull/2224#discussi... https://github.com/w3cping/tracking-issues/issues/53#issuecomment-653541639 https://github.com/w3cping/tracking-issues/issues/53#issueco... >As I said, I can't use RFP, it breaks too many sites. Weird. I only know a few sites that break with RFP on, and I don't use them frequently.
- gruez 6y ago>Take Canvas fingerprints. If you added a bit of randomness to how the browser renders pixels, the fingerprint would change each time you measured it. It would still be unique, but it would be a useless tracking tool. that doesn't work because the sites can just take multiple samples and average the results.
- gitgud 6y agoThis is very similar to how OS's and Browsers have mitigated the spectre vulnerabilities last year. They basically fuzz (randomize) the timing precision that you can do, so you can't use timing to leak information across 2 different processes. >"As of Firefox 57.0.4, Mozilla was reducing the resolution of JavaScript timers to help prevent timing attacks, with additional work on time-fuzzing techniques planned for future releases." https://en.m.wikipedia.org/wiki/Spectre_(security_vulnerability) https://en.m.wikipedia.org/wiki/Spectre_(security_vulnerabil... Maybe similar tactics could help prevent finger-printing!