Look into the Tor Browser design document to pick new elements for "Firefox: Privacy Related "about:config" Tweaks"

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

The Tor Browser design document: https://www.torproject.org/projects/torbrowser/design/#Implementation

An example: privacy.resistFingerprinting should be set to true.

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)

---

• privacy.resistFingerprinting = true (A result of the Tor Uplift effort, this preference makes Firefox more resistant to browser fingerprinting.)
• privacy.firstparty.isolate = true (A result of the Tor Uplift effort, this preference isolates all browser identifier sources (e.g. cookies) to the first party domain, with the goal of preventing tracking across different domains.)

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

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/Tracking

Note that this was the only pref not mentioned in the design document, so I guess I did all the work then for this part.

[ghost]

https://gist.github.com/Shifterovich/ba649d96a1618cad294bc9b47f0541c8

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

@Shifterovich
Thanks, I'll look into it later to see what we can squeeze from it in addition here.

[ghost]

A post from my now-dead blog. I did some research on browser fingerprinting in general.

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

Two first ones are addressed in this pull: https://github.com/privacytoolsIO/privacytools.io/pull/284

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

@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

[Atavic]

There are tickets dealing with privacy.resistFingerprinting and privacy.firstparty.isolate.

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

@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.

[Atavic]

You can choose those only, yes. There's a lot of comments.

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

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?

[ghost]

Waiting for approval.

[privacytoolsIO]

Approved.