naresh97/trojan-rs

A Trojan proxy implementation written in Rust. Optimizing for size.

trojan-rs

To circumvent certain firewalls, I previously used trojan-go which worked pretty well. Unfortunately, the binary size of around 8MB was slightly too large to use on my portable router runnin OpenWRT. So I decided to write an implementation of the Trojan Client/Server in Rust.

The goal is to keep the binary under 1MB.

Based on the Trojan protocol described here.

Usage

Modify client.toml and server.toml appropriately. See samples.

trojan-rs [OPTIONS] <COMMAND> [ADAPTER]

Commands:
  server  runs the Trojan Server
  client  runs the Trojan Client with the specified adapter

Options:
  --config <FILE>   defaults to "./server.toml" or "./client.toml"
  --log             defaults to INFO
                    values: DEBUG, INFO, WARN, ERROR

Adapter:
  --adapter <ADAPTER_TYPE>  used in client mode
                            defaults to socks5
                            values: socks5 tun

Architecture

On the client side:

CLIENT <-> SOCKS5 SERVER <-> TROJAN CLIENT <-> INTERNET

On the server side:

INTERNET <-> TROJAN SERVER  <-> SERVER
                            <-> FALLBACK

trojan-rs's Issues

add conditional compilation for client/server binaries to reduce size

added feature flag 'vendored' for including openssl for native-tls

with this feature enabled in Cargo.toml, it is able to cross compile musl static target with cargo-zigbuild

added multiplexing support

able to specify config file path from cli args

Implement port 80 redirection

Currently, the server will not listen on port 80, therefore HTTP requests will fail. Implement a listener on Port 80 that will send a REDIRECT to the HTTPS site

tproxy support

I see that tun was added, i guess it is used to do global proxy without setting proxy for individual program, to be honest, tproxy is much faster than tun.

added websocket support

able to specify log level as cli arg

udp does not work

trojan protocol can handle udp traffic, but this software does not support UDP.

For example dig @1.1.1.1 example.com via socks5 proxy.

able to create tun device and route traffic through it

Fallback not working correctly when websockets enabled

unified server domain and port in server.toml

Implement simple fileserver for the fallback

Currently the use must provide an external resource, ie. apache webserver to server fallback content. Implementing a simple file server will allow the user to implement a static website as a fallback without external tools

trojan client<->server connection lacks ipv6 support

requires trojan server configuration to be modified to allow listening on IPv4 as well as IPv6 addresses