Editing How to bypass ISP censorship (section)

= Obfuscated Proxy Protocols & Platforms =
This category represents the “engine” for most modern, robust circumvention. The development of these protocols illustrates the “cat-and-mouse” arms race.

# '''Phase 1 (Encrypt):''' Standard VPNs (OpenVPN, WireGuard) are encrypted but have obvious “fingerprints”.
# '''Phase 2 (Scramble):''' Tools like Shadowsocks and obfs4 encrypt and “scramble” traffic to look like “random” data.
# '''Phase 3 (Mimic):''' Tools like V2Ray (VLESS+TLS) and Trojan are designed to mimic standard, benign HTTPS traffic.
# '''Phase 4 (Be Indistinguishable):''' Tools like Naïve Proxy reuse the actual network stack from a real browser (Chrome) to be bit-for-bit indistinguishable.

== [https://shadowsocks.org/ Shadow Socks] ==
A fast, encrypted SOCKS5 proxy. It is not a full VPN. Originally created in 2012 by “clowwindy” specifically to bypass the Great Firewall (GFW) of China. Its strength is its simplicity and its use of modern AEAD ciphers. It “disguises” traffic to look like HTTPS but does not explicitly mimic another protocol.

'''PROs:'''
* <span style="color:green">'''Fast and Lightweight:'''</span> Generally faster than full VPNs and complex multi-layered tools.
* <span style="color:green">'''Selective:'''</span> Easy to configure which traffic goes through it (e.g., using a PAC file).

'''CONs:'''
* <span style="color:red">'''Detectable by Advanced DPI:'''</span> Advanced DPI can detect Shadowsocks traffic through traffic analysis and active probing.
* <span style="color:red">'''Not a Full VPN:'''</span> Does not tunnel all system traffic by default, leading to potential “leaks”.

== [https://github.com/v2fly/v2ray-core V2Ray] ==
A platform or framework for building proxies. It is not a single protocol, but a “box” that can manage multiple inbound and outbound protocols, transports, and advanced routing rules. By wrapping its proxy traffic inside Web Socket and TLS, it makes the traffic appear as standard, indistinguishable HTTPS traffic.

'''PROs:'''
* <span style="color:green">'''Extremely Flexible:'''</span> Can be configured to mimic HTTPS, run over Web Sockets, use QUIC, etc.
* <span style="color:green">'''Resilient:'''</span> Its multiprotocol nature means it can be reconfigured if one method is blocked.
* <span style="color:green">'''Advanced Routing:'''</span> Can selectively route traffic based on domain or IP.

'''CONs:'''
* <span style="color:red">'''Complex:'''</span> Requires understanding of its complex concepts of inbounds, outbounds, and transports.
* <span style="color:red">'''Performance Overhead:'''</span> Layered encryption adds significant latency.
* <span style="color:red">'''VMess is Detectable:'''</span> The original VMess protocol is now considered detectable by advanced GFW packet sniffing.

=== V2Ray Protocols: VMess vs. VLESS ===
* '''VMess:''' The original, feature-rich protocol for V2Ray. It has its own built-in encryption and authentication methods. It is considered more “heavy” and less safe against modern GFW probing.
* '''VLESS:''' A newer, lightweight protocol. It removes VMess's built-in encryption layer and delegates security to the underlying transport layer, such as TLS. This simplifies the handshake, improves speed, and makes it more indistinguishable from a standard HTTPS website.

== [https://github.com/XTLS/Xray-core X-ray] ==
A high-performance, open-source proxy platform and a fork of V2Ray. Developed by the XTLS community. Xray-core supports all of V2Ray's protocols and adds XTLS. XTLS is a “direct encryption” technology that avoids the performance-draining “TLS-in-TLS” problem, resulting in lower latency and higher speeds than VLESS+TLS.

'''PROs:'''
* <span style="color:green">'''Faster:'''</span> X-ray with its XTLS protocol is generally considered faster and more efficient.
* <span style="color:green">'''Backward Compatible:'''</span> Acts as a drop-in, enhanced replacement for V2Ray-core.
* <span style="color:green">'''Advanced Protocols:'''</span> VLESS and XTLS are highly effective at mimicking standard web traffic.

'''CONs:'''
* <span style="color:red">'''Complexity:'''</span> Inherits all of V2Ray's complexity.
* <span style="color:red">'''Less Documentation:'''</span> Newer technology with poorer documentation than established setups.

== [https://github.com/trojan-gfw/trojan Trojan] ==
A proxy protocol that is specifically designed to perfectly imitate a real HTTPS server. It runs on a server, binds to port 443, and simultaneously serves a real, working website. This makes it highly resistant to the “active probing” techniques.

'''PROs:'''
* <span style="color:green">'''Extremely Stealthy:'''</span> Mimics HTTPS perfectly and serves a real website as a disguise.
* <span style="color:green">'''High Performance:'''</span> Simpler protocol that uses TLS directly.

'''CONs:'''
* <span style="color:red">'''Requires a Domain Name:'''</span> You must have a registered domain name and a valid SSL/TLS certificate.
* <span style="color:red">'''Vulnerable to TLS-in-TLS Detection:'''</span> Censors have started detecting the “TLS-in-TLS” pattern.

== [https://github.com/klzgrad/naiveproxy Naïve Proxy] ==
A proxy that re-uses the network stack from the Chromium browser to camouflage its traffic. A “Phase 4” tool. It uses HTTP/2 multiplexing, HTTP/2 traffic padding, and the exact TLS handshake of a real Chrome browser.

'''PROs:'''
* <span style="color:green">'''The “Most” Stealthy:'''</span> Arguably the most advanced tool for defeating traffic analysis and fingerprinting.
* <span style="color:green">'''High Performance:'''</span> Leverages Chrome's high-performance HTTP/2 stack.

'''CONs:'''
* <span style="color:red">'''Complex:'''</span> Requires a Caddy server with a specific plugin, domain name, and TLS cert.
* <span style="color:red">'''Still a Proxy:'''</span> Not a full system-wide VPN.