+9
日增长
9,648
stars
1,050
forks
122
watchers
56
prs
748
issues
152
releases
README
NaïveProxy !build workflow
NaïveProxy uses Chromium's network stack to camouflage traffic with strong censorship resistance and low detectability. Reusing Chrome's stack also ensures best practices in performance and security.
The following traffic attacks are mitigated by using Chromium's network stack:
Website fingerprinting / traffic classification: mitigated by traffic multiplexing in HTTP/2 and parroting preambles.
TLS parameter fingerprinting: defeated by reusing Chrome's network stack.
Active probing: defeated by application fronting, i.e. hiding proxy servers behind a commonly used frontend server with application-layer routing.
Length-based traffic analysis: mitigated by padding and fragmentation.
Architecture
[Browser → Naïve client] ⟶ Censor ⟶ [Frontend → Naïve server] ⟶ Internet
NaïveProxy uses Chromium's network stack to parrot traffic between regular Chrome browsers and standard frontend servers.
The frontend server can be any well-known reverse proxy that is able to route HTTP/2 traffic based on HTTP authorization headers, preventing active probing of proxy existence. Known ones include Caddy with its forwardproxy plugin and HAProxy.
The Naïve server here works as a forward proxy and a packet length padding layer. Caddy forwardproxy is also a forward proxy but it lacks a padding layer. A fork adds the NaïveProxy padding layer to forwardproxy, combining both in one.
Download NaïveProxy
Download here. Supported platforms include: Windows, Android (with Exclave, husi, NekoBox), Linux, Mac OS, and OpenWrt (support status).
Users should always use the latest version to keep signatures identical to Chrome.
Build from source: Please see .github/workflows/build.yml.
Server setup
The following describes the naïve fork of Caddy forwardproxy setup.
Download here or build from source:
sh
go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest
~/go/bin/xcaddy build --with github.com/caddyserver/forwardproxy=github.com/klzgrad/forwardproxy@naive
Example Caddyfile (replace user and pass accordingly):
{
order forward_proxy before file_server
log {
exclude http.log.error Avoid logging user activity
}
}
:443, example.com {
tls [email protected]
encode
forward_proxy {
basic_auth user pass
hide_ip
hide_via
probe_resistance
}
file_server {
root /var/www/html
}
}
:443 must appear first for this Caddyfile to work. See Caddyfile docs for customizing TLS certificates. For more advanced usage consider using JSON for Caddy 2's config.
Run with the Caddyfile:
sudo setcap cap_net_bind_service=+ep ./caddy
./caddy start
See also Systemd unit example and HAProxy setup.
Client setup
Run ./naive with the following config.json to get a SOCKS5 proxy at local port 1080.
json
{
"listen": "socks://127.0.0.1:1080",
"proxy": "https://user:[email protected]"
}
Or quic://user:[email protected], if it works better. See also parameter usage and performance tuning.
Third-party integration
v2rayTop issues
Latest release
v154.0.8037.49-5 v154.0.8037.49-5 2026-10-22Block compromised eMudhra intermediates. ALL USERS MUST UPGRADE as old versions are no longer safe from MitM attack using forged eMudhra certificates.