diff --git a/content/knowledge/Commercial VPN Use Cases.md b/content/knowledge/Commercial VPN Use Cases.md index c9492e9..6b145c3 100644 --- a/content/knowledge/Commercial VPN Use Cases.md +++ b/content/knowledge/Commercial VPN Use Cases.md @@ -56,49 +56,64 @@ A VPN is useful in a variety of scenarios, such as: ## Circumventing censorship/filters {#circumventing-censorship} -Network filtering can take many forms, from simplistic DNS or IP blocklists to sophisticated deep packet inspection ({{< rawhtml >}}DPI{{< /rawhtml >}}). A VPN, if not itself blocked, is the most robust method to circumvent filtering, but other methods may also be worth considering: + -
GoodbyeDPI or PowerTunnel
+Network filtering can take many forms, from simplistic DNS or IP blocklists to sophisticated deep packet inspection ({{< abbr "DPI" />}}). A VPN, if not itself blocked, is the most robust method to circumvent filtering, but other methods may also be worth considering: -
VPN on port tcp/443
+Encrypted DNS +: - Bypasses unsophisticated DNS blocks only + - Easily thwarted by unsophisticated IP address or [{{< abbr "SNI" "Server Name Identification" />}}](https://www.cloudflare.com/learning/ssl/what-is-sni/) blocks + - Increases fingerprintability + - Free and easy ([Quad9](https://quad9.net/service/service-addresses-and-features), [Cloudflare 1.1.1.1](https://developers.cloudflare.com/1.1.1.1/encryption/), [Google Public DNS](https://developers.google.com/speed/public-dns/docs/secure-transports)) -
Obfuscation proxy: Shadowsocks, obfs4, or V2Ray (VMess)
+[GoodbyeDPI](https://github.com/ValdikSS/GoodbyeDPI) or [PowerTunnel](https://github.com/krlvm/PowerTunnel) +: - Works for HTTP(S) traffic only + - Attempts to work around DPI by exploiting bugs in DPI software + - May increase fingerprintability + - Free and does not rely on external servers -
VPN over obfuscation proxy
+Remote desktop +: - Requires significant trust in the endpoint + - TLS terminates at the endpoint + - All browsing and usage data can be easily scraped by the endpoint sysadmin + - Limited practicality + - High latency and subject to compression artifacts + - Greater hardware requirements for the endpoint + - Limited commercial availability -
Tor
- -{{< /rawhtml >}} \ No newline at end of file +VPN on port tcp/443 +: - Rarely port-blocked (default port for HTTPS), but detectable with DPI + - Slow due to encapsulation with TCP + - Cannot use WireGuard (requires UDP) + - Offered by many commercial VPN providers ([IVPN](https://www.ivpn.net/knowledgebase/troubleshooting/how-do-i-change-the-port-or-protocol-used-to-connect/), [Mullvad](https://mullvad.net/en/help/connection-speed-why-it-so-slow/), [Proton VPN](https://protonvpn.com/support/udp-tcp/)) + +Obfuscation proxy: [Shadowsocks](https://shadowsocks.org/), [obfs4](https://gitlab.com/yawning/obfs4), [V2Ray](https://www.v2fly.org/en_US/) (VMess), [Xray](https://github.com/XTLS/Xray-core) +: - Specifically designed for obfuscating traffic from DPI + - Functionally very similar to VPNs, including encrypted transport + - Security implications generally less explored than VPNs + - Limited commercial availability outside of specific regions + +VPN over obfuscation proxy +: - Increased latency compared to standalone proxy + - More complex setup for self-hosting + - Offered by some commercial VPN providers ([IVPN](https://www.ivpn.net/knowledgebase/troubleshooting/i-cant-connect-from-china-or-vietnam-or-iran-etc-how-do-i-enable-obfsproxy/), [Mullvad Bridges](https://mullvad.net/en/help/intro-shadowsocks/)) + +Tor [pluggable transports](https://tb-manual.torproject.org/circumvention/) +: - Works for TCP traffic only (UDP tunneling over Tor is [complicated, fragile, and counterproductive](https://www.whonix.org/wiki/Transporting_UDP_Tunnels_over_Tor)) + - Slowest option for clearnet access + - Free and decentralized + +See also [Great Firewall Report](https://gfw.report/)'s highly technical reports on Shadowsocks, V2Ray, and other censorship-related topics. + +--- + +_Note that attempting to circumvent government censorship or network filters may come at significant risk to life and property. It is up to every individual to carefully balance their need for access against the potential implications of being discovered, including by a log‑now-decrypt‑later approach. While the authors and team of PrivSec.dev support open and uncensored internet access for all, we cannot assume any responsibility or liability for consequences that may arise from the pursuit thereof._ + +