Fingerprinting protection doesn't work in FF67, try https://amiunique.org
Firefox 67 is suppose to block fingerprinting when activated in the security/privacy settings. Well, try this french site : https://amiunique.org and see what can be read from your system and browser. I'm wondering how can it be possible to block fingerprinting other than giving false/random/generic data and be like everyone, not unique...
Solution eye eponami
It depends on what is giving you away as "unique". In the details for "My fingerprint" you can identify what gives you a low "Similarity ratio" and then obfuscate those variables. These may have side-effects. For example, both my content language and my timezone have a SR < 0.1% — I could change these, but these may have undesirable side-effects I'm not prepared to tolerate.
Tanga eyano oyo ndenge esengeli 👍 0All Replies (4)
Solution eye oponami
It depends on what is giving you away as "unique". In the details for "My fingerprint" you can identify what gives you a low "Similarity ratio" and then obfuscate those variables. These may have side-effects. For example, both my content language and my timezone have a SR < 0.1% — I could change these, but these may have undesirable side-effects I'm not prepared to tolerate.
That's what I thought, you can't avoid fingerprinting :-( without side-effects. How then does the fingerprint protection work in FF67? Mozilla shouldn't give users a false sense of protection if the efficiency is too low...
According to [this post] the fingerprinting protection looks to be based on a server blacklist rather than analysing server behaviour:
"How will Firefox block these harmful scripts?
To combat these threats, we are pleased to announce new protections against fingerprinters and cryptominers. In collaboration with Disconnect, we have compiled lists of domains that serve fingerprinting and cryptomining scripts…"
(I must admit, I'm surprised at this, I thought it was based on server behaviour too.)
Ezalaki modifié na Damon
[...] the fingerprinting protection looks to be based on a server blacklist rather than analysing server behaviour[...]
Ah, I see... It's indeed a good start and it answers my question. But Mozilla should warn it's users that the protection is partial.
This post should be marked with SOLVED.
Thank you!