-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[SUGGESTION] Add option to enable browser fingerprinting defenses #3125
Comments
Personally, I believe this is best left until it is more mature (at the very least). It will get an option in the preferences UI anyway, hopefully with a "Learn more" link. The target AFAIK is for 59 (since the next TBB will be based on ESR59). If you add it, then due diligence means keeping up to date with the changes it causes and providing some info - and there is a LOT (including conflicts with existing prefs) ... and a LOT more to come. I would leave this in Mozilla's hands For an idea of the scope of explaining this to people - see arkenfox/user.js#7 .. for an idea of how this can conflict with existing prefs and alter your intended fingerprint, see arkenfox/user.js#222 PS: looks like it will change from boolean to integer, as will Edit: I meant "as will privacy.firstparty.isolate" |
Duplicate of #2381. |
Describe the issue
Tom added an option to enable browser fingerprinting defenses by setting
privacy.resistFingerprinting = true
https://bugzilla.mozilla.org/show_bug.cgi?id=1397611 with the goal that "privacy tools can toggle it on and take advantage of the work we've been doing."This has been added for Firefox 58 so it's not until that time that one can take advantage of this.
Also see his patch: https://reviewboard.mozilla.org/r/177158/diff/2#index_header
The text was updated successfully, but these errors were encountered: