Tor Uplift: https://wiki.mozilla.org/Security/Tor_Uplift/Tracking
Part of the Tor Uplift Project has been the creation of a privacy.resistFingerprinting preference, to which more and more code solutions are being tied to. This issue is so we can discuss, track and implement these are they come up rather than creating numerous issues or constantly going back to old ones
DONE
COMING
user.js issues that are related:
New tor ticket on keyboard fingerprinting (this one is about keypress leaking) - https://trac.torproject.org/projects/tor/ticket/21390 . Ticket links to a very nice test page: https://w3c.github.io/uievents/tools/key-event-viewer.html with lots of options for output.
@Roman-Nopantski By enabling the Proposed Field in the key-event-viewer page, it shows a %LOCALE% column.
I found this page from _W3 Consortium_: https://w3c.github.io/fingerprinting-guidance/#detectability
Is Canvas Fingerprinting going to be included ?
@uBlock-user If you go to the Tor Uplift page linked in the first comment, it is listed. It's been there for over 7 months (on Tor Uplift), and may or may not be added. Hopefully it will be. Currently still unassigned. https://bugzilla.mozilla.org/show_bug.cgi?id=1041818 , "take steps to mitigate canvas fingerprinting" (2.5 years old) - what that solution eventually is, who knows (they mention making it "click to play" and a site permission), but mention nothing about faking a random. I think you're best off with the extension TBH.
Edit: I should add that the above list is items that are going to be tied to the privacy.resistFingerpinting preference. It may well be that in time canvas is tied to that as well.
Yes you're right, it appears so. ScriptSafe covers it all. Also I don't suppose Chromium devs would be interested in adding this ?
There's an ungoogled-chromium discussion.
I guess this issue is continued at https://github.com/ghacksuserjs/ghacks-user.js/issues/7, so I'll close it here.
Hello folks,
privacy.resistFingerprinting prevent log into ff accounts...
privacy.resistFingerprinting prevent log into ff accounts...
I don't have a Firefox account myself. Can someone confirm this? If the problem persist, maybe you should open a new issue about it.
Most helpful comment
New tor ticket on keyboard fingerprinting (this one is about keypress leaking) - https://trac.torproject.org/projects/tor/ticket/21390 . Ticket links to a very nice test page: https://w3c.github.io/uievents/tools/key-event-viewer.html with lots of options for output.