-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reducing Panopticlick fingerprint score #372
Comments
Changing useragent can break Websites and make you more unique so i wouldnt recommend that |
From what I've read setting "privacy.resistFingerprinting" to "false" causes the Firefox window not to be set to a generic size (at start), thus making your Firefox more unique if you have it set to a custom width/size. At this point I'm beginning to doubt the Panopticlick score values... (just my two cents ofc ;)) |
In TBB it is |
Panoptclick gives its results over the pool of the browsers that have been submit to the test. That's a subset of common browser: just look at the results in an indicative way (feel happy when you are not unique) and try to blend in the biggest pool possible. |
Looks panoptclick doesnt work with temporary container, i just got that i have a strong protection, but no details. |
It seems like the whole window size protection is still broken in Firefox. At least on 60.2.2esr. |
I have been looking to reduce the Panopticlick fingerprint score through experimenting with various settings.
So far I have found that these 2 reduce the bit score:
With these two applied at the end of the
user.js
I achieve a score of 7.9 in Firefox.I still can't find a single browser for which "Is your browser accepting Do Not Track commitments?" to show something different from "no". I have asked EFF by email many days ago but no reply at all.
Out of the box TBB with security slider set to max security shows a score of 6.57 bits. I wonder which particular prefs may help to achieve that in FF too and if there are any settings which may help to reduce it even more.
Any ideas?
The text was updated successfully, but these errors were encountered: