Re:Browser Fingerprinting: An Introduction and the Challenge...
by jlmorton on Wednesday September 04, 2019 @08:35PM
(#20882815)
Even with `privacy.resistFingerprinting` enabled, my fingerprint is unique all-time on https://amiunique.org.
[ Parent
| on HN ]
Re:Browser Fingerprinting: An Introduction and the Challenge...
by Quarrel on Thursday September 05, 2019 @08:05AM
(#20885813)
I wouldn't put much stock in amiunique right now. It might be great, but needs a bigger sample size.
I am unique purely based on my content language: "en-AU,en,en-US"
While we like to think we're special in Australia, I'm not THAT special.
Re:Browser Fingerprinting: An Introduction and the Challenge...
by raxxorrax on Thursday September 05, 2019 @07:53AM
(#20885752)
With the option being enabled, there is 1 other guy that creates the exact same fingerprint. I hope he is not a serial killer...
Currently using chrome for HN, but that also creates a completely unique print. I highly doubt it will ever be a focus of this browser to change that issue. And everyone should buy more widescreen monitors, they are awesome.
I wonder if users of standard devices like iPhones fare much better. Not that I would want to use one...
Curiously, Firefox gives me WebGL Vendor = not supported, which isn't true at all, while chrome gives the full driver name, which in my case is very uncommon (using an intel nuc).
Re:Browser Fingerprinting: An Introduction and the Challenge...
by jdc on Wednesday September 04, 2019 @10:42PM
(#20883426)
It seems to me that the Navigator interface is a pretty rich source of info for fingerprinting. For instance, even if I spoof my user-agent in the HTTP request, Navigator gleefully exposes the real one anyway.
Re:Browser Fingerprinting: An Introduction and the Challenge...
by shakna on Wednesday September 04, 2019 @10:19PM
(#20883323)
There's also other fingerprinting that you need to be aware of, like keeping the browser a default size rather than maximising it and giving away how big your screen is.
Re:Browser Fingerprinting: An Introduction and the Challenge...
by Santosh83 on Thursday September 05, 2019 @03:15AM
(#20884547)
Currently you will need to outright disable Javascript to defeat fingerprinting, and it will stay that way unless browsers actually cooperate and standardize ways to present a unified API and default values.