diff --git a/4.1-Extensions.md b/4.1-Extensions.md index 13e462c..d511f9b 100644 --- a/4.1-Extensions.md +++ b/4.1-Extensions.md @@ -96,7 +96,7 @@ These extensions will not mask or alter any data sent or received, but may be us - Replacing _some version specific_ 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 over three years out of date and would not likely be used anyway * Cookie extensions - - ❗️Sanitizing in-session is a false sense of privacy. They do 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_ full sanitizing _and_ a new IP. The same applies to Firefox + - ❗️Sanitizing in-session is a false sense of privacy. [They do nothing for IP tracking](https://educatedguesswork.org/posts/traffic-relaying/). Even Tor Browser does not sanitize in-session e.g. when you request a new circuit. A new ID requires _both_ full sanitizing _and_ a new IP. The same applies to Firefox - ❗️Cookie extensions can lack APIs or implementation of them to properly sanitize - e.g. at the time of writing: [Cookie Auto Delete](https://addons.mozilla.org/firefox/addon/cookie-autodelete/) - > As of Firefox 86, strict mode is not supported at this time due to missing APIs to handle the Total Cookie Protection