Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent UA Client hints #160

Closed
scoricov opened this issue Jul 28, 2022 · 3 comments
Closed

Prevent UA Client hints #160

scoricov opened this issue Jul 28, 2022 · 3 comments

Comments

@scoricov
Copy link

Hello,

This proposal is already implemented in Chrome: https://wicg.github.io/ua-client-hints/#intro
Example:

SEC-CH-UA: ".Not/A)Brand";v="99", "Google Chrome";v="103", "Chromium";v="103"
SEC-CH-UA-MOBILE: ?0
SEC-CH-UA-PLATFORM: "macOS"

This means the true UA and platform information leaks aside from the UA header which this extension is meant to control.

Solution for Chrome:

var settings = new CefSettings(); settings.CefCommandLineArgs.Add("disable-features", "UserAgentClientHint"); Cef.InitializeAsync(settings); 

Would it be possible to include it in the extension's code?

@ray-lothian
Copy link
Owner

The next release will delete all "sec-ch-" headers;

https://github.com/ray-lothian/UserAgent-Switcher/blob/master/v2/firefox/common.js#L561

@r3a1d3a1
Copy link

Wouldn't deleting it altogether look suspicious as well?
Setting it to the latest version of Chrome (most used Browser) on Windows (most used OS) should be less conspicuous.

ray-lothian added a commit that referenced this issue Nov 14, 2022
@ray-lothian
Copy link
Owner

In the new implementation, the extension exposes the correct values instead of deleting them when the "navigator.userAgentData" object is present. If not, they get removed.

ray-lothian added a commit that referenced this issue Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants