Skip to content
This repository has been archived by the owner on Nov 22, 2022. It is now read-only.

serious privacy leak, browser signature #34

Closed
ghost opened this issue Mar 17, 2013 · 1 comment
Closed

serious privacy leak, browser signature #34

ghost opened this issue Mar 17, 2013 · 1 comment
Assignees

Comments

@ghost
Copy link

ghost commented Mar 17, 2013

Please consider https://panopticlick.eff.org/ - the result is that every single orweb user can be identified.

The biggest problems:

  • User-agent should be set to a value that is widely used and not unique. The default "android" will frequently include details like brand, model and build number. Predefined "Firefox5" is does not appear to match any real world browser.
  • HTTP headers: seems utf-16 is the privacy culprit here, rarely ever used and pehraps should be filtered
  • screen-size/color-depth gives away too much of information.
@ghost ghost assigned n8fr8 May 28, 2013
@n8fr8
Copy link
Member

n8fr8 commented May 29, 2013

User-agent: we know use the Samsung Galaxy SII user-agent as the default, since that is the most common Android device. We have also updated iPhone and Firefox to the values specified by EFF's Panopticlick report as the most "anonymous" values for those browser.

HTTP Header: we are overriding accept headers now, so the utf-16 value is not there, and are now using a common default set of headers.

screen-size/color-depth is determined via javascript, and is difficult to block unless you turn off javascript. We will not be addressing that issue in the short term.

@n8fr8 n8fr8 closed this as completed May 29, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant