Browser Fingerprinting
sites.google.com
Browser Fingerprinting
1–10 of 46 posts
Re: Browser Fingerprinting
#2Re: Browser Fingerprinting
#3Re: Browser Fingerprinting
#4Using multiple VMs with diverse connectivity, one can sidestep all "Explicitly assigned client-side identifiers" and "Machine-specific characteristics". For evading WebGL, VM OS diversity is essential. It's harder to obscure "User-dependent behaviors and preferences", especially mouse and keyboard stuff. But it helps to switch keyboards, and between using mouse and touchpad.
Re: Browser Fingerprinting
#5Is there a way to easily change (some) browser plugins every five minutes, so fingerprinting becomes useless?
Re: Browser Fingerprinting
#6Once talked with over a beer with a web performance head of company X, he said that you can use the web performance profile - without looking at any other browser identifiers - to pretty accurately do browser fingerprinting. When you then look additionally at the interaction speed within an webapp you can even profile different users.
Re: Browser Fingerprinting
#7Is there a way to easily change (some) browser plugins every five minutes, so fingerprinting becomes useless?
You could load your browser through Selenium and explicitly choose which plugins to load but I wouldn't call it easy. Definitely not accessible to the average user.
Re: Browser Fingerprinting
#8https://panopticlick.eff.org/
My font set was completely unique, which I partly expected. However, my canvas fingerprint was also completely unique, which did surprise me.
Re: Browser Fingerprinting
#9Is there a way to easily change (some) browser plugins every five minutes, so fingerprinting becomes useless?
You could load your browser through Selenium and explicitly choose which plugins to load but I wouldn't call it easy. Definitely not accessible to the average user.
Perhaps somebody could write a plugin which changes identity (as seen by the fingerprinter) every so often.
Re: Browser Fingerprinting
#10Once talked with over a beer with a web performance head of company X, he said that you can use the web performance profile - without looking at any other browser identifiers - to pretty accurately do browser fingerprinting. When you then look additionally at the interaction speed within an webapp you can even profile different users.
Jesus... is anyone actually doing this? Extremely interesting!