spoofdpi is a cross-platform proxy tool that bypasses Deep Packet Inspection (DPI) by fragmenting and desynchronizing TLS handshakes. It operates in three modes: HTTP proxy, SOCKS5 proxy, or TUN interface (transparent proxy). In production, it intercepts outgoing connections, reads the TLS ClientHello, splits it into segments using configurable strategies (SNI-split, random, chunk, first-byte, or custom plans), optionally sends fake packets before the real data, and may disorder segments by manipulating the TTL field so that DPI middleboxes misparse the connection while the destination server reassembles it correctly. It also includes a built-in DNS resolver with UDP, HTTPS (DoH), and system backends, and a rule system for per-domain/per-IP configuration. The architecture is a single Go binary with modular internal packages: config (TOML+CLI loading), desync (TLS/UDP desynchronization), dns (multi-backend resolver), netutil (connection management, dialing, TTL setting), packet (raw packet capture/injection via pcap or Linux raw sockets), proto (HTTP, SOCKS5, TLS parsing), rule (domain and CIDR matching), server (HTTP, SOCKS5, TUN server implementations), session (context-based tracing), trie (generic trie structures), cache (sharded LRU and TTL caches), and logging (zerolog-based structured logging). The TUI mode uses bubbletea for a terminal interface showing real-time speed and logs. Key entry points are cmd/spoofdpi/main.go (main function) which parses CLI flags, loads configuration, and starts the selected server. External dependencies include gopacket for packet manipulation, wireguard-tun for TUN device support, gvisor for TCP/IP stack in TUN mode, and various Go packages for CLI, TOML, DNS, and logging. The code is well-structured with extensive use of interfaces, generics, and concurrency primitives (context, channels, goroutines).
Hiddify-Manager is a comprehensive anti-censorship proxy/VPN management system designed for multi-user environments. It orchestrates a suite of proxy cores (Xray, Sing-Box, HAProxy, Nginx, WireGuard, etc.) via systemd services, a Flask-based web panel, and a CLI tool. The system supports over 20 protocols (VLESS, VMess, Trojan, Shadowsocks, Reality, Telegram proxies, DNS tunnels) and is optimized for regions with heavy internet censorship (Iran, China, Russia). It provides automated installation, configuration generation via Jinja2 templates, multi-node support, Docker deployment, and cloud-init/Terraform scripts for cloud provisioning. The codebase is actively maintained with frequent updates, but contains deprecated services and a large shell script surface that introduces maintenance complexity.
Se7en Pro is a Windows 10/11 anti-censorship VPN client that aggregates eleven circumvention protocols into one desktop application. In production it runs a Flutter glassmorphic GUI (Se7enFlutter) that talks over authenticated named pipes to a .NET 8 daemon (Se7enCore), which orchestrates child processes for Psiphon, Tor, Xray/sing-box, Aether (MASQUE/WireGuard/WARP), and SHARD (Cloudflare TLS fragmentation over VLESS/Trojan nodes). Chained multi-hop modes (Psiphon-over-WARP, Tor-over-V2Ray, etc.) are first-class features, and a Wintun/tun2socks TUN adapter provides system-managed routing with split tunneling by app, domain, and IP along with a kill switch, system proxy, DNS handling, LAN sharing, and admin elevation. Architecturally the daemon's ConnectionManager selects active engines behind an IConnectionEngine abstraction; LocalSocksEngineBase supplies a shared process-spawn/SOCKS5-probe/auto-restart lifecycle for every engine. The Flutter side is a Riverpod-driven dashboard with live speed/ping telemetry, engine-filtered log viewing, region picking, and a large settings surface. Primary data flows are: UI command → PipeCoreClient → IpcDaemonService JSON dispatch → ConnectionManager → engine process → local SOCKS5/HTTP proxy → system proxy or TUN; status and logs stream back over the same pipe. The daemon persists settings to settings.json, caches Aether edge pools, and fetches SHARD node lists from GitHub. The repo is hybrid in a narrow sense: it bundles curated operational datasets (Akamai/Cloudflare/Fastly IP ranges, Akamai seed IPs, SHARD seed nodes, Tor bridge strings) used at runtime for CDN fronting and edge discovery. These are static resource inputs to the application machinery, not research artifacts or pipeline outputs, so the dominant character is application. Craftsmanship is solid but uneven. The engine abstraction, IPC layer, Authenticode trust checks, DPAPI secret storage, and route-pinning logic are genuinely reusable. However, multi-thousand-line widget files (settings_page.dart ~2200 lines, split_tunnel_section.dart ~1200 lines), incomplete i18n coverage with hardcoded English/Chinese/Russian strings, version drift (UI reports v1.0.4 while the engine UA says 1.1.0), brittle relative resource paths, and bundled third-party binaries with limited update channels create real maintenance friction. Test coverage is thin (a few model/round-trip widget tests).
This repository is a static collection of proxy subscription links and configuration files for V2Ray and Clash proxy clients. It contains a README.md with promotional material for various VPN services, a list of free proxy URIs in v.txt, a Clash YAML configuration file (c.yaml) with hundreds of proxy entries, and a vpn.md with a promotional link. The repository serves as a free source of proxy configurations for circumventing internet censorship. It does not contain any original software code. The architecture is trivial: it is a file-based subscription endpoint. The primary data flow is users downloading these files and importing them into proxy clients.