20.11 bits of identifying info in Panopticlick test
Reported by
stu...@anchev.net,
Jan 31 2018
|
|||||
Issue descriptionChrome Version : 64.0.3282.119 OS Version: openSUSE Leap 42.3 URLs (if applicable) : https://panopticlick.eff.org/ Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Tor: 6.57 bits (with factory settings) Firefox 58: 9.7 bits (with additional strengthening using https://github.com/pyllyukko/user.js/) IceCat: 7.9 bits (with factory settings) What steps will reproduce the problem? 1. Create new browser profile with settings as described in bug #795526 2. https://panopticlick.eff.org/ 3. Run the test What is the expected result? The browser should protect from fingerprinting and provide relevant settings for additional privacy in regards to that. What happens instead of that? 20.11 bits of identifying info - more than the average as per EFF's whitepaper. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36
,
Feb 2 2018
Reporter@ Thanks for the issue. As this issue is related to Privacy, adding TE-NeedsTriageHelp and requesting someone from Privacy team to please look into this issue and help in further triaging. Thanks..
,
Sep 27
,
Oct 24
Thanks, George. I'm working on reducing the fingerprinting surface of Chrome. I'd like to avoid breaking (too many) websites though, which makes this a difficult task. Issue 860229 is a very small step in that direction, but I hope there'll be more progress soon.
,
Oct 29
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jan 31 2018