It is possible to track based on the re-use of TLS session information. Firefox has a way to stop this, using a hidden setting. It does not appear that there is any eqiuvalent in Chromium. EFF’s Privacy Badger has an issue requesting turning off of session-id reuse. Could you do this in Brave?
Related Topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Protection against HTTPS session tracking | 1 | 453 | October 10, 2019 | |
Brave stops worries, not tracking - my experience testing brave privacy promises | 7 | 4327 | February 4, 2024 | |
Does & will Brave protect us from HTML5 click tracking/auditing? | 6 | 892 | June 7, 2019 | |
In this report we detail our novel user tracking mechanism that leverages Trust Tokens | 1 | 822 | December 24, 2021 | |
Strip tracking parameters (utm, fbclid) | 4 | 1940 | July 6, 2021 | |
New cookies management on Brave beta | 3 | 1494 | February 25, 2024 | |
Does Brave remove the tracking ID built in to Chromium? | 2 | 733 | March 5, 2020 | |
How to make brave undetectable, reduce fingerprintability, and improve privacy | 2 | 296 | June 28, 2024 |