-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Remove navigator.connection
from Brave-core
#20122
Comments
Test Plan:
|
For QA, i've also added a test for this in the QA suite: https://dev-pages.brave.software/dom-properties.html |
Verified
Followed the steps above. Steps:
|
Verification passed on Samsung Tab A with Android 10 running 1.35.77 x64 Beta build
|
See brave/brave-browser#20122 Potential improvements: return a generic value, return a farbled generic value. Or modify the values somehow. Radek observed: * downlink is never greater than 10, sometimes values like 9.3 * downlinkMax can be greater than 10, e.g. 100/infinity * effectiveType: computed from rtt and downlink * saveData can be important for users trying to limit downloaded data
Chromium allows sites to learn about local network conditions by querying
navigator.connection
. This is privacy harming information. It can be used by fingerprinters, as well as by more determined attackers to potentially learn about user traveling patterns (including when the user is at home or not).Ideal behavior here would be for the below to both be true in all shields configurations:
navigator.connection === undefined
"connection" in window.navigator === false
An ideal implementation would also include a brave://flags option (default off) that advanced users could use to re-enable the API. The flag description should have text mentioning that the functionality risks their privacy.
The text was updated successfully, but these errors were encountered: