Anti fingerprinting measures need an update

Brave Feature Requests Desktop Requests
1

Brave’s anti-fingerprinting is good. I believe at one point the anti webgl fingerprinting was enough in 2020, however modern gpu based telemetry like the exact gpu you use is still given away to websites. When combined with other information leaks it becomes very easy for a website to track you from site to site. All hardware specific data should be obscure and or randomized as it is a major tracking point. If the amazing devs at brave could use a tool like browserleaks.com to check what escapes and patch, brave will be hands down the best browser in every aspect. until then, hardened firefox is better at blocking this type of telemetry.

2

For anybody who drops by … According to Brave Search (Answer with AI):

To test Brave’s WebGL fingerprinting protections, you might use BrowserLeaks and the Electronic Frontier Foundation (EFF) Cover Your Tracks test.

  • BrowserLeaks WebGL Test: Visit browserleaks.com/webgl to view your current WebGL vendor and renderer hashes. With Brave’s default Shield settings, these values should appear randomized or “undefined” compared to other browsers, indicating protection is active.

  • EFF Panopticlick: Visit panopticlick.eff.org to check if your browser is fingerprintable. Brave aims for the WebGL hash to be “undetermined” or distinct from your actual hardware to prevent identification.

  • Canvas Test: Visit browserleaks.com/canvas to verify that canvas fingerprinting is also blocked, as these protections often work in tandem.

How to Verify:

  1. Open the test site in Brave.

  2. Click the Lion Icon (Shields) in the address bar.

  3. Ensure Fingerprinting Protection is toggled ON (set to Standard or Aggressive).

  4. Refresh the page; the fingerprint values should change or show as randomized/undefined, confirming the shield is interfering with the fingerprinting script.

Note: If a specific site requires WebGL to function (e.g., a 3D game or map), you may need to temporarily disable Shields for that specific domain, as aggressive WebGL blocking can break legitimate functionality.

(AI-generated answer. Please verify critical facts.)