📡 TCP over HTTP

Forked from stable version, changes: add https and cross compile support.

🥦 The Questions

🪃 What does it do?

You can proxy TCP traffic over HTTP.

An basic setup would be:

[Your TCP target] <--TCP--  [Exit Node]
                                 ^
                                 |
                               HTTP
                                 |
[Your TCP client] --TCP--> [Entry Node]

🍩 Why?

I was bored.

This allows you to reach servers behind a HTTP reverse proxy.
Suddenly you can do SSH to a server which is behind a NGINX proxy.

If you have for example a HTTP gateway, you can now also have a TCP gateway.

🍾 Why not?

Converting binary to base64, send it via HTTP and convert it back is inefficient and pretty slow.
Less than 10MB/s slow.

Also, if a server only opens port 80, nobody expects you to tunnel through and rech the SSH server.
Security wise, no admin would want this tool on his/her server without him/her knowing.

This tool is more a proof of concept. Don't take it too serious.

🎺 Usage

Replace tcp-over-http by cargo run -- if you have not installed the binary.

tcp-over-http --help

# Start our exit node to reach our SSH server (default listen localhost:8080)
tcp-over-http exit --help
tcp-over-http exit --target-host localhost --target-port 22

# Start our entry node (default listen localhost:1415)
tcp-over-http entry --help
tcp-over-http entry --target-url http://localhost:8080/

# Test it
ssh localhost -p 1415

⌚️ Performance

This package is not optimized for stability or speed.

Setup

# Terminal 0 - Netcat listening
nc -l 1234 > /dev/zero

# Terminal 1 - Exit Node
tcp-over-http exit --target-host locahost --target-port 1234

# Terminal 2 - Entry Node
tcp-over-http entry --target-url http://localhost:8080/

# Terminal 3 - Sending random data
# Using pipeviewer (pv) to see current data rate
time dd if=/dev/random bs=1M count=1024 | pv | nc localhost 1415 -q 0

🏅 Result: 6MiB/s