gdr / tuntox (public) (License: GPLv3) (since 2017-01-24) (hash sha1)
Tunnel TCP connections over the Tox protocol

/README.md (06443ef9e58ea5f86c6fd1d88a4efe53378a50fa) (6178 bytes) (mode 100644) (type blob)

## Introduction

Tuntox is a program which forwards TCP connections over the [Tox](https://tox.chat/) protocol. This allows low-latency access to distant machines behind a NAT you can't control or with a dynamic IP address.

Tuntox is a single binary which may run in client mode or server mode. As a rule of thumb, run the server on the remote machine you want to access and the client on your local computer from which you want to access the server.

**Tuntox is in early work in progress stage**. It won't kill your goats but it may segfault, leak memory or have security issues (although I tried to make it rather secure). It won't be as fast as it could be because of the tremendous amount of debug output.

If you don't know what Tox is - it's an instant messenger protocol which is fully P2P, supports audio/video calls and file transfers. Unlike Skype it's fully open and unlike, say, XMPP - the calls and file transfers actually work. Go download a client from http://utox.org/ or read more at https://tox.chat/

[![Coverity Scan Build Status](https://scan.coverity.com/projects/5690/badge.svg)](https://scan.coverity.com/projects/5690) [![Travis Build Status](https://travis-ci.org/gjedeer/tuntox.svg?branch=master)](https://travis-ci.org/gjedeer/tuntox) 

## Binary

Get the binaries from Releases tab on github. Just download the correct file for your architecture, execute chmod +x and you're done. The binaries are signed with my PGP key, [11C1 B15A 5D5D D662 E469 928A EBDA 6B97 4ED3 D2B7](https://keybase.io/gdr).

If you miss the times when men wrote their own device drivers, see BUILD.md.

## Running the server

Run the Tuntox server on a laptop which connects via 3G, on your home computer behind six NATs or on your Raspberry Pi. No ports need to be forwarded to its public IP - the machine will be accessible via the Tox overlay network.

    ./tuntox

runs the server in the foreground. When the server starts, it will print its Tox ID to the output - note it, you will need it later to access the machine from outside.

If you terminate the server (Ctrl-C) and start again, it will generate a new Tox ID and you'll need to write it down again. It kind of defeats the purpose, so you'll want to help the server store its Tox ID somewhere. By default it saves a file in /etc/tuntox/, so if you create this directory and chown it so that it's accessible to tuntox, it will have a fixed Tox ID. 

Alternatively you may use the -C switch instead:

    ./tuntox -C /path/to/the/config/directory/

To daemonize on startup, add -D:

    /path/to/tuntox -D

Or, if you run something like supervisord or systemd, you're welcome to contribute a configuration file for the system of your choice (see #3, #4, #6). There's absolutely no need to run the server as root.

## Client

So, the laptop now has the Tuntox server installed. How do you connect to it?

	./tuntox -i <ToxID> -L 2222:127.0.0.1:22

where `<ToxID>` is the ID you noted down when setting up the server. You didn't forget to write it down, did you?

After you run this command, open a second terminal window and execute:

	ssh -p 2222 myuser@localhost

Magic, port 2222 on your localhost is now the SSH server on the machine which runs the Tuntox server.

The -L switch works (almost) the same way it does in SSH. For the uninitiated, -L A:B:C means "forward port C on ip B to port A on localhost". Unlike SSH, you can't use hostnames for B (unless you link the binary dynamically).

Alternatively, SSH ProxyCommand mode works too:

	ssh -o ProxyCommand='./tuntox -i <ToxID> -P localhost:22' gdr@localhost

Fun stuff: [VPN over Tox](VPN.md)

Client can be ran as a regular non-root user, [unless A < 1024](https://www.linuxquestions.org/linux/articles/Technical/Why_can_only_root_listen_to_ports_below_1024) ("A" is the local port). There's a [workaround](http://unix.stackexchange.com/a/10737) available.

## Security / threat model

**TUNTOX IS NOT SECURE WITHOUT THE -s SWITCH.** Supply *-s yourpassword* both on the server and the client, and you will be fine. This switch is introduced in 0.0.4, codename "Mr. Lahey's Got My Porno Tape!". Even better, run `TUNTOX_SHARED_SECRET=yourpassword tuntox ...` on both sides.

The Tuntox server generates a new Tox ID on every startup, or saves its private key in a file. Anyone who wants to connect to this server needs its Tox ID, which consists of the publicly-known pubkey and a secret 32-bit "antispam" value. Then, the client sends a shared secret which is then compared to the secred supplied on server's command line. If they don't match, friend request is left unanswered.

Therefore, posession of the server's Tox ID and a secret should be considered equivalent to posession of an Unix account with SSH access. Tuntox does not implement remote shell capability, but it is possible that it's exploitable.

PSK authentication is optional but recommended - it's only enabled when -s switch is present on server side or the TUNTOX_SHARED_SECRET environment variable is set. PSK is sent as Tox friend request message - as far as the author understands libtoxcore code, it's encrypted using server's public EC key.

The Tuntox Server can optionally allow only whitelisted ToxIDs. Supply *-i yourallowedtoxid* one time or more to add a ToxID to the whitelist. Note: The default client behavior is to generate a new ToxID for every run (because author thinks it's a nice privacy feature). You will want to use the -C switch in client to force reading a saved identity from tox_save.

Tuntox is piggybacking on the Tox protocol, which itself has not been audited by security researchers. Tox crypto has been implemented with libsodium (which is based on Bernstein's NaCl) and thus uses the ecliptic curve 25519 for key exchange and salsa20 for stream encryption. According to the author's best knowledge, libsodium makes it as hard as possible to get crypto wrong, but we don't know until Tox has been audited.

## License

Sorry about GPLv3 - both toxcore and utox (from which I borrowed some code) are GPLv3.

Thank you to the toxcore and utox developers without whom this program would never exist.

Thank you Mr_4551 for your help and motivation.


Mode Type Size Ref File
100644 blob 281 8b6eea76cbea14a93132b1ec7744f471c073041c .gitignore
100644 blob 2232 779127eb84583c6e30ed2819e9cc4d0188e8180f .travis.yml
100644 blob 869 59799b0ded35ed81dcaf0e4a32fcf974a0339836 BUILD.md
100644 blob 35058 2061be2b732ea86101a7c0d5f4df0bbbfb830a30 LICENSE.md
100644 blob 1003 b1c2466b30e755efc7fe0b30fbc367d2dc743103 Makefile
100644 blob 637 ee41cdaf376b4cb8eca51751b170e4c698167dda Makefile.mac
100644 blob 6178 06443ef9e58ea5f86c6fd1d88a4efe53378a50fa README.md
100644 blob 1947 73faf4c548715f81d33894e531868bc672f30ac3 VPN.md
100644 blob 19197 aaa3f67c50eda0587d47c485c80de3de2e076be7 client.c
100644 blob 719 db71d40fb0270358a0fe473be54812acd544b6a4 client.h
100644 blob 3956 44281c9e202e8688cad141b05ec6a02364a3dc69 generate_tox_bootstrap.py
100644 blob 176 52f9d71f3415d613e0cf73edd6d05a2a27fdfd8a gitversion.c
100644 blob 3141 31244349cd221b4e8931f612b3325ae59faa58cb log.c
100644 blob 892 bcd4c9bb1af0a1f1c44b1e7a36c3a5971ba73b34 log.h
100644 blob 549 a9095f6b9cc0f97ddc698e07a4606b37822ba61c mach.c
100644 blob 287 5ac9a4e29fbb831ba2cfa6dc98589ffaf381b91b mach.h
100644 blob 45077 4d211d78d98e3251056ca663a6b8ddc847195783 main.c
100644 blob 3316 106525fa1bb0e36f8e2083fa9ca65bd20803ef7c main.h
040000 tree - 463f5d075b76a903cb9fe172d23282a883192491 scripts
100644 blob 38687 0f8d1422ab80d562bf2ed4cb614502645b1a62a1 tox_bootstrap.h
100644 blob 12536 75e9dc5ed9399120416e8da5f24d1ccde41cf901 utarray.h
100644 blob 61492 7205c67efa27c66884c8d4d1c8a105d4854a0548 uthash.h
100644 blob 4007 b1353b303b803c8c37fc4e5f7cd0f9710159a942 util.c
100644 blob 638 7dced6b423b39797c2589660864ea61cc34d5416 util.h
100644 blob 55882 b5f3f04c104785a57d8280c37c1b19b36068e56e utlist.h
100644 blob 11555 867442c843dbe6bf096a488e3ce9ec6323809f7f utstring.h
Hints:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/gdr/tuntox

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/gdr/tuntox

Clone this repository using git:
git clone git://git.rocketgit.com/user/gdr/tuntox

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main