Remove DOMHighResTimeStamp privacy.reduceTimerPrecision value for localhost / 127.0.0.1 hosts
Categories
(Core :: Privacy: Anti-Tracking, enhancement)
Tracking
()
People
(Reporter: mowod66703, Unassigned)
References
(Depends on 1 open bug)
Details
Steps to reproduce:
Remove rounding policy for DOMHighResTimeStamp for privacy.reduceTimerPrecision value for localhost / 127.0.0.1 hosts, so every call to performance.now / Date.now will get real values
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•2 years ago
|
||
I think exempting the protection from the localhost page can cause a potential loophole. If a user loads a page that contains fingerprinting scripts on localhost, the fingerprint can be sent to attackers via fetch.
I suggest adding a separate pref to control the behavior on the localhost page instead of disabling it from localhost pages.
If a user loads a page that contains fingerprinting scripts on localhost, the fingerprint can be sent to attackers via fetch.
Not for file:// protocols, for that still be restrictions. Only for localhost domain names, as it is for devs only, so they will know what they do, casual users will not be able to run anything locally, downloaded pages will be opened via file:// schema
As here pointed localhost is trusted and secure
https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts
Description
•