Look into the Tor Browser design document to pick new elements for "Firefox: Privacy Related "about:config" Tweaks" #272
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#272
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Tor Browser design document: https://www.torproject.org/projects/torbrowser/design/#Implementation
An example:
privacy.resistFingerprinting
should be set totrue
.Maybe this is a bad idea, and maybe suggesting that one should tweak the Tor Browser itself to use clearnet as an alternative to Firefox + about:config tweaks.
Anyway, discuss. I'll compile a list in the meantime: (complete)
We should also consider reviewing the Tor Uplift project since some prefs aren't documented in the Tor Browser Design document, such as
privacy.firstparty.isolate
. https://wiki.mozilla.org/Security/Tor_Uplift/TrackingNote that this was the only pref not mentioned in the design document, so I guess I did all the work then for this part.
https://gist.github.com/Shifterovich/ba649d96a1618cad294bc9b47f0541c8
@Shifterovich
Thanks, I'll look into it later to see what we can squeeze from it in addition here.
A post from my now-dead blog. I did some research on browser fingerprinting in general.
Two first ones are addressed in this pull: https://github.com/privacytoolsIO/privacytools.io/pull/284
@Shifterovich
There's a feature request that is now in the review phase https://bugzilla.mozilla.org/show_bug.cgi?id=967895 which will integrate the HTML5 Canvas blocking inside Firefox, not sure if default but there will be for sure some pref for this, in which case Canvas Blocker would no longer be needed and you can close this issue, https://github.com/privacytoolsIO/privacytools.io/issues/99
There are tickets dealing with privacy.resistFingerprinting and privacy.firstparty.isolate.
@Atavic Oh, ghacks' user.js :) Might be a good idea instead of having the tiresome manual approach but it will require auditing all their options, we only want privacy related ones.
You can choose those only, yes. There's a lot of comments.
Reviewed all options, seems those two are the only ones that stick out. @Shifterovich Is there anything preventing the merge for https://github.com/privacytoolsIO/privacytools.io/pull/284?
Waiting for approval.
Approved.