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 dvpn

Browse Source
This commit is contained in:
mfwmyfacewhen 2023-05-18 14:51:05 -05:00 committed by Daniel Gray
parent 0a2c0d9697
commit 87a3dbed9f
No known key found for this signature in database
GPG Key ID: 41911F722B0F9AE3
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -89,6 +89,12 @@ 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.
## 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. Multi-hop is needed to solve this, but that comes with a stability and performance cost.
Another consideration is legal liability; the exit node will need to deal with legal problems from misuse of the network, an issue that the Tor network has contended with for its entire existence. This disincentivizes regular people from running nodes and makes it more attractive for a malicious actor with lots of resources to host one. This is a big problem is the service is single-node, as the potentially malicious exit node can see who you are and what you're connecting to.
## Sources
- [VPN - a Very Precarious Narrative](https://schub.io/blog/2019/04/08/very-precarious-narrative.html) by Dennis Schubert