An implementation of HTTP Tunnel in Rust.
The core code is entirely abstract from the tunnel protocol or transport protocols.
In this example, it supports both HTTP
and HTTPS
with minimal additional code.
It can run over QUIC+HTTP/3
or connect via another tunnel (as long as AsyncRead + AsyncWrite
is satisfied for the implementation).
configuration.rs
- contains configuration structures + a basic CLI
config/
with configuration files/TLS materialshttp-tunnel_codec.rs
- a codec to process the initial HTTP request and encode a corresponding response.upstream.rs
- an abstraction + basic TCP implementation to connect upstream servers.
TTL
)relay.rs
- relaying data from one stream to another, tunnel = upstream_relay + downstream_relay
relay_policy
tunnel.rs
- a tunnel. It's built from:
HttpTunnelCodec
)main.rs
- application. May start HTTP
or HTTPS
tunnel (based on the command line parameters).
logs/application.log
(log/
contains the actual output of the app from the browser session)logs/metrics.log
- very basic, to demonstrate the concept.`There are two modes.
HTTPS
:
$ cargo fmt && cargo clippy && cargo test
$ cargo build --release
$ ./target/release/http-tunnel --config ./config/config.yaml --bind 0.0.0.0:8443 https --pk "./config/domain.pfx" --password "6B9mZ*1hJ#xk"
HTTP
:
$ cargo fmt && cargo clippy && cargo test
$ cargo build --release
$ ./target/release/http-tunnel --config ./config/config-browser.yaml --bind 0.0.0.0:8080 http
In Firefox, you can set the HTTP proxy to localhost:8080
. Make sure you run it with the right configuration:
https://support.mozilla.org/en-US/kb/connection-settings-firefox
(use HTTP Proxy and check "use this proxy for FTP and HTTPS")
$ ./target/release/http-tunnel --config ./config/config-browser.yaml --bind 0.0.0.0:8080 http
This proxy can be tested with cURL
:
Add simple.rust-proxy.org'
to /etc/hosts
:
$ echo '127.0.0.1 simple.rust-http-tunnel.org' | sudo tee -a /etc/hosts
Then try access-listed destinations (see ./config/config.yaml
), e.g:
curl -vp --proxy https://simple.rust-http-tunnel.org:8443 --proxy-cacert ./config/domain.crt https://www.wikipedia.org
You can also play around with destinations that are not allowed.
The application cannot see the plaintext data.
The application doesn't log any information that may help identify clients (such as IP, auth tokens). Only general information (events, errors, data sizes) is logged for monitoring purposes.
Slowloris
attack (opening tons of slow connections)Some of them can be solved by introducing rate/age limits and inactivity timeouts.