Live data from Hacker News

Protections Against Fingerprinting and Crypto Mining in Firefox Nightly and Beta

blog.mozilla.org

1–10 of 246 posts

Re: Protections Against Fingerprinting and Crypto Mining in Firefox Nightly and Beta

#4
I really welcome Mozilla's effort in fighting the uphill battle against browser fingerprinting. I am however very interested in the terms of Mozilla's partnership with Disconnect. Are obsoleting their add-on for Firefox out of the good of their hearts?

Re: Protections Against Fingerprinting and Crypto Mining in Firefox Nightly and Beta

#7
post #2

Kind of a shame that I can't browse that site using a VPS on a tier-2 VPS provider (Vultr)

Can you elaborate on why you cannot browse that site? From your comment it is not clear to me what the problem is but it reads as if you are trying to blame mozilla.

Re: Protections Against Fingerprinting and Crypto Mining in Firefox Nightly and Beta

#9
post #4

I really welcome Mozilla's effort in fighting the uphill battle against browser fingerprinting. I am however very interested in the terms of Mozilla's partnership with Disconnect. Are obsoleting their add-on for Firefox out of the good of their hearts?

If I'm not mistaken, Firefox's currently built-in Tracking Protection also borrows from the base Disconnect blocking lists. So this would not be the first time they've used them.

Re: Protections Against Fingerprinting and Crypto Mining in Firefox Nightly and Beta

#10
post #6

Seems like they're just using a blacklist? Those seem to be able to be gamed pretty trivially.

Agreed. Setting up blacklists is just whack-a-mole. I'd be more interested in detection of actual fingerprinting techniques, such as system font enumeration using canvas, or WebGL GPU fingerprinting. It would be technically possible to detect the creation of WebGL or canvas contexts that aren't actually rendered in the layout and prevent data gathered from those contexts from being sent in any XHR payload. I'm sure that's a lot of work.

Maybe it would be better to find the worst offending JS APIs and demand a user consent step similar to webcam or notifications in order for the scripts to run at all.

Post reply on HN