Installer trojan-go avec Homebrew, MacPorts, Nix

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• trojan-go

Historique du projet

Trojan-Go's history is best understood as an extension-oriented reimplementation rather than a wholly separate protocol. Its README emphasizes compatibility with the original Trojan feature set, including TLS tunneling, UDP proxying, transparent proxy modes, detection-resistance mechanisms, MySQL persistence, user authentication, traffic statistics, and quota controls.

The Go implementation then adds features aimed at real-world deployment friction: a simplified mode, automatic SOCKS5/HTTP proxy adaptation, TProxy support, smux multiplexing, custom routing, WebSocket-over-TLS for CDN transit, TLS fingerprint handling, gRPC APIs, pluggable transports, Shadowsocks AEAD-style secondary encryption, and YAML configuration.

Historique d'adoption

The official README points users to precompiled release binaries, Docker deployment, and a Telegram feedback group. It also names graphical clients that support Trojan-Go extensions, including Qv2ray and Igniter-Go, while noting compatibility with original Trojan clients when extension-only features are not used.

This adoption history is concentrated in the proxy/censorship-circumvention tooling niche rather than general networking. Package managers such as Homebrew, MacPorts, and Nix make the daemon easier to install on developer machines and small servers, while the README's cross-compilation examples show interest in routers, Raspberry Pi, and other constrained targets.

Modes d'utilisation

The README documents quick server and client startup flags, conventional config-file operation with `trojan-go -config config.json`, URL-based client startup, and Docker deployment with host-mounted configuration. It shows separate server and client examples and provides both JSON and YAML client/server config examples.

Package users typically install the binary, write a server or client config, and run it as a local proxy, transparent proxy, relay, or daemon. The package is useful to operators who want the Trojan ecosystem with a single Go binary and extra transports such as WebSocket over TLS.

Pourquoi les passionnés de paquets s'y intéressent

Trojan-Go is package-nerd-significant because it is a protocol-compatible reimplementation that exposes many deployment choices through one binary. It is also an example of proxy tooling where packaging, release binaries, Docker images, and cross-compilation all matter because users deploy the same tool on desktops, servers, routers, and small devices.

Its Homebrew formula is especially relevant for macOS users who want to test or operate proxy tooling without manually downloading release archives from GitHub.

Chronologie

• Original Trojan compatibility: README documents compatibility with the original Trojan protocol and config format.
• Extension phase: README documents multiplexing, routing, WebSocket-over-TLS, AEAD, gRPC API, transport plugins, and YAML config.
• Current README: precompiled binaries, Docker deployment, quick-start flags, and config-file operation are documented as primary usage paths.

Related projects

• Trojan, Qv2ray, Igniter-Go, Shadowsocks AEAD, smux, v2ray-plugin

Sources

• https://github.com/p4gefau1t/trojan-go#readme
• https://p4gefau1t.github.io/trojan-go