Git-Mirrors/privacyguides.org
1
0
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2025-04-23 00:29:23 -04:00
Code Issues Packages Projects Releases Wiki Activity

add odoh

Browse Source
This commit is contained in:
mfwmyfacewhen 2023-05-19 17:40:37 -05:00 committed by Daniel Gray
parent 6e910ed218
commit 5008042079
No known key found for this signature in database
GPG Key ID: 41911F722B0F9AE3
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/basics/vpn-overview.md
View File

@ -89,6 +89,8 @@ Multi-Party Relays use multiple nodes owned by different parties, such that no i
MPRs seek to solve a problem inherent to VPNs: the fact that you must trust them completely.
MPRs typically have ways of protecting your DNS traffic. Apple's Private Relay uses ODoH, INVISV uses Obvlivious DNS, and Tor lets the exit node do the DNS lookup for you.
## Decentralized VPNs
Another attempt at solving the issues with centralized VPN services are dVPNs. These are based on blockchain technology and claim to eliminiate trust in a single party by distributing the nodes across lots of different people. However, many times a dVPN will default to a single node, meaning you need to trust that node completely, just like a traditional VPN. Unlike a traditional VPN, this one node that can see all your traffic is a random person instead of your VPN provider that can be audited and has legal responsiblities to uphold their privacy policy. Multi-hop is needed to solve this, but that comes with a stability and performance cost.