Menu

Browser Fingerprinting Protection: Randomize, Blend In or Block
📰

Browser Fingerprinting Protection: Randomize, Blend In or Block

DEV Community·ParallaxGrain·17 days ago
#r3livAq9
#security#privacy#browser#fingerprint#webdev
Reading 0:00
15s threshold

A page can ask the browser which graphics card it runs on, through WebGL, the browser's 3D graphics interface. An unprotected browser answers with the exact model. Brave answers with one word, "Brave", for the vendor and the renderer alike. That is deliberate: Brave decided the model is too identifying to give out, which makes it the simplest case of browser fingerprinting protection.

A fingerprint works for a tracker only when it is distinctive (few other browsers match it) and stable (it survives from one session to the next). Defenses go after one or the other, and most browsers mix them.

A browser can make your fingerprint shared, shifting or unreadable. It can't make it disappear, because a page can't render without reading some of those values.

Three kinds of browser fingerprinting protection

Blend in. Many browsers report identical values, so the fingerprint stops being distinctive: it points to a crowd instead of a person. Tor Browser and Mullvad Browser are built on this.

Keep changing.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.