-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
Update Brave Fingerprint settings #2641
Conversation
✅ Your preview is ready!
|
@@ -288,7 +288,7 @@ Brave allows you to select additional content filters within the internal `brave | |||
|
|||
- [x] Select **Strict** under *Upgrade connections to HTTPS* | |||
- [x] (Optional) Select **Block Scripts** (1) | |||
- [x] Select **Strict, may break sites** under *Block fingerprinting* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused by this change, in the version I have of Brave (latest from their RPM repo) it says "Strict, may break sites".
I guess this would be a question to pose to the Brave team, perhaps a legacy flag that didn't get changed in their RPM repo? On MacOS and Windows I don't see the option anymore. Also, besides the links above regarding their announcement about this change, brave/brave-browser#35541 here's the relevant desktop release that mentions the removal of this option. brave/brave-browser#31229 Here the relevant issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The visibility of that option is at the moment controlled by a flag (brave://flags/#brave-show-strict-fingerprinting-mode
). It defaults in the C++ code to true
and is set to false
by Griffin (also known as a "variations" server in Chromium terms). So on first start it will be visible (because the Griffin changes have not taken effect yet), but it will go away as soon as the browser restarts.
brave/brave-browser#39517 is the issue tracking the removal of the flag.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am seeing this change on Linux (latest from APT repo) and macOS 👍
Brave simplifies fingerprinting option, removes "strict" option https://brave.com/privacy-updates/28-sunsetting-strict-fingerprinting-mode/ Signed-off-by: Jonah Aragon <[email protected]> Signed-off-by: Daniel Gray <[email protected]>
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
Brave switched to just a toggle regarding fingerprinting a while ago, as outlined here: https://brave.com/privacy-updates/28-sunsetting-strict-fingerprinting-mode/
Also being discussed here: https://discuss.privacyguides.net/t/brave-removes-strict-fingerprinting-protection/16302
Changes proposed in this PR:
Contribution terms (click to expand)
1) I am the sole author of this work. 2) I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project. 3) I have disclosed any relevant conflicts of interest in my post. 4) I agree to the Community Code of Conduct.