privacyguides/privacyguides.org
1
1
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2026-09-28 09:32:31 +00:00
Code Issues Activity

update: clarify Tor and Mullvad Browser capabilities (#3272)

Browse Source 
Update wording to accurately reflect tracking and fingerprinting
protections. Adjust descriptions regarding anonymity, fingerprint
similarity, and advanced tracking mitigation.

Signed-off-by: Daniel Gray <dngray@privacyguides.org>
This commit is contained in:
fria
2026-09-15 07:28:05 +09:30
committed by Daniel Gray
parent 8be53ef24b
commit e40376173a
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/advanced/tor-overview.md
+1 -1
View File
@@ -92,7 +92,7 @@ It is critical to understand the difference between bypassing censorship and eva
### Tor Browser is not the most *secure* browser
Anonymity can often be at odds with security: Tor's anonymity requires every user to be identical, which creates a monoculture (e.g., the same bugs are present across all Tor Browser users). As a cybersecurity rule of thumb, monocultures are generally regarded as bad: Security through diversity (which Tor lacks) provides natural segmentation by limiting vulnerabilities to smaller groups, and is therefore usually desirable, but this diversity is also less good for anonymity.
Anonymity can often be at odds with security. Tor achieves anonymity by ensuring every user appears identical, creating a digital monoculture where the same vulnerabilities exist across all installations. In cybersecurity, monocultures are generally considered a risk. Security through diversity provides natural segmentation by limiting the impact of an exploit to a smaller segment of users. While such diversity is structurally desirable for security, it inherently compromises user anonymity by making individuals trackable.
Additionally, Tor Browser is based on Firefox's Extended Support Release builds, which only receives patches for vulnerabilities considered *Critical* and *High* (not *Medium* and *Low*). This means that attackers could (for example):