PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2025-02-20 18:31:35 -05:00
Code

Multihop

Browse Source 
Signed-off-by: tommytran732 <contact@tommytran.io>
This commit is contained in:
tommytran732 2022-08-22 10:37:35 -04:00 committed by Tommy
parent 28306561d6
commit 6510a36e10
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/providers/Choosing Your VPN Provider.md
View File

@ -41,7 +41,13 @@ Beyond just reading the documentation from your VPN provider, you should also ch
## Multi-Hopping ## Multi-Hopping
This feature is not a must, but it is very nice to have. Not all VPN providers own their hardware, datacenter, and network [WIP] This feature is not a must, but it is very nice to have.
Not all VPN providers own their hardware, datacenter, and network . In fact, if your check their network, most VPN providers end to rent their servers from different service providers. This means that beyond trusting the VPN provider, you are also trusting their providers to not monitor your traffic.
By using using multihop, you can minize the risk of being monitored by your VPN provider's service providers. Your packets are encrypted at least twice and routed through at least 2 hops, with the entry node only knowing who you are but not what you visit, and with the exit node only knowing what you visit but not who you are. This cannot protect you from a malicious VPN provider as they will just compromise the VPN server on both ends, but it can help against a single node compromise (caused by a rougue datacenter employee for example).
Ideally, you should choose two servers from two different countries when using this feature.
## Pluggable Transport ## Pluggable Transport