Any website can access a selection of Firefox resource files to find out more about the web browser that is used to connect to the site.
Firefox and add-ons use the resource:// scheme to load resources internally, but some of the information are available to sites the browser connects to as well.
It is unclear why websites would need access to resource:// resources.
See Fix Firefox resource URI leak
Addon: no-resource-uri-leak
Thanks! I kinda hope Mozilla would come up with a fix to this.
Direct links:
I'll add this to the README.
I think there's not much we can do to fix this besides recommending to use the add-on, so I'll close this issue.
FYI: plugging the resource://URI leak but allowing functionality for addons etc is part of the tor uplift and will be tied to the privacy.resistFingerprinting preference (actually a lot of stuff will be tied to that pref)
Rather than create new issues - I'll list em here, an you can decide what to do with the info
Coming
I was wondering if it would be a good idea to create an open issue for tracking the tor uplift items bound to resistFingerprinting, because we're now well past just resource://URIs
additional to the above last post
And, I'll just add this here: spoof timezone as UTC
Indeed the privacy.resistFingerprinting seems to be a promising switch that'll enable all kinds of privacy goodies.
Sure. Sounds like a good idea. I take it that you volunteered to create the issue? :)
Done. Feel free to add labels and fix the title :)
Thanks!
Most helpful comment
FYI: plugging the resource://URI leak but allowing functionality for addons etc is part of the tor uplift and will be tied to the
privacy.resistFingerprintingpreference (actually a lot of stuff will be tied to that pref)Rather than create new issues - I'll list em here, an you can decide what to do with the info
Coming
// https://trac.torproject.org/projects/tor/ticket/8725
// https://bugzilla.mozilla.org/show_bug.cgi?id=863246
// test: https://www.browserleaks.com/firefox
// https://bugzilla.mozilla.org/show_bug.cgi?id=1217290
// https://bugzilla.mozilla.org/show_bug.cgi?id=1222285