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

Ability to neutralize User-Agent string for enhanced privacy #100

Closed
gorhill opened this issue Dec 25, 2013 · 5 comments
Closed

Ability to neutralize User-Agent string for enhanced privacy #100

gorhill opened this issue Dec 25, 2013 · 5 comments
Milestone

Comments

@gorhill
Copy link
Owner

gorhill commented Dec 25, 2013

Re. privacy.

Because the Chrome API doesn't allow more than one extension to change the outgoing headers, and since HTTPSB must already potentially change the outgoing headers (to remove cookies), this means that using another extension to change the User-Agent string alongside HTTPSB won't work. So HTTPSB must provide this feature, or else a user will have to forfeit one on the two extensions.

@ghost
Copy link

ghost commented Dec 31, 2013

I'm not sure what you mean by "neutralize". Does this mean to block sending the user-agent at all? I'm afraid this would have contra-productive effects to impeding fingerprinting.

A better solution would be "rotating" user-agents, i.e. a new user-agent is used, e.g., every 30 minutes or with every new browser session.

@gorhill
Copy link
Owner Author

gorhill commented Dec 31, 2013

No I didn't have in mind nulling the field, I had in mind removing or altering some fields which contribute too much bits of fingerprint info based on panopticlick's results.

In any case, after looking at all this I may choose to have this option handled by a companion extension of HTTPSB. The HTTP referer made sense because it is based on the rules. But here the matrix has nothing to do with this, so I am thinking of having this handled in a different companion extension which would be able to take over the task of changing the outgoing headers (can only be done by one extension) from HTTPSB.

@ghost
Copy link

ghost commented Dec 31, 2013

No I didn't have in mind nulling the field, I had in mind removing or altering some fields which contribute too much bits of fingerprint info based on panopticlick's results.

Okay, but whatever you decide don't forget that even removing some fields can make your browser (more) unique as 99.999% of other users don't do that. Rotating user-agents would not have that problem ...

@gorhill
Copy link
Owner Author

gorhill commented Jan 1, 2014

"whatever you decide don't forget that even removing some fields can make your browser (more) unique"

Yes, hence my emphasis on reducing bits of info. In any case I now lean toward not including this, as there is no relation whatsoever to the matrix, I see this more as a companion extension to HTTPSB.

@ghost ghost assigned tailHey Jan 29, 2014
@gorhill
Copy link
Owner Author

gorhill commented Feb 10, 2014

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants