From eb1cdee05df56dab9d91f372a509518623e07262 Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Sat, 27 Nov 2021 05:31:28 +0000 Subject: [PATCH] Updated 4.1 Extensions (markdown) --- 4.1-Extensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/4.1-Extensions.md b/4.1-Extensions.md index 9383cc9..9bc8898 100644 --- a/4.1-Extensions.md +++ b/4.1-Extensions.md @@ -65,7 +65,7 @@ These extensions will not mask or alter any data sent or received, but may be us - Replacing scripts on CDNs with local versions is not a comprehensive solution and is a form of [enumerating badness](https://www.ranum.com/security/computer_security/editorials/dumb/). While it may work with some scripts that are included it doesn’t help with most other third party connections - CDN extensions don't really improve privacy as far as sharing your IP address is concerned and their usage is fingerprintable as this Tor Project developer [points out](https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/22089#note_2639603). They are the [wrong tool](https://en.wikipedia.org/wiki/XY_problem) for the job and are not a substitute for a good VPN or Tor Browser. Its worth noting the [resources](https://git.synz.io/Synzvato/decentraleyes/-/tree/master/resources) for Decentraleyes are hugely out of date and would not likely be used anyway -❗️ Sanitizing in-session is a false sense of privacy. Extensions may lack APIs or application of them, and it does nothing for IP tracking. If this is your threat model, use the Tor Browser +❗️ Sanitizing in-session is a false sense of privacy. Extensions may lack APIs or application of them, and it does nothing for IP tracking. Even Tor Browser does not sanitize in-session e.g. when you request a new circuit. A new ID requires _both_ a new sanitized session _and_ a new IP. The same applies to Firefox. * Temporary Containers - Redundant with Total Cookie Protection (dFPI) or FPI