No description
Find a file
Erèbe - Romain Gerard 0ec27e9d27 fix typo in debug log in the HTTP proxy
Former-commit-id: 3a5b68b568058848a84c5801e99be1e3d11f2675
Former-commit-id: b9c43a5b446e9c3fde4e9016864e036b1c97dfba [formerly 7cf2553244e5ff0af1c729564905ab05d072720f] [formerly 0a79f27e64df05797d06a8da9bf7543c84e86ed7 [formerly 5599e859e906704ab0d6b0a65658a4aeb8403f8e [formerly 5599e859e906704ab0d6b0a65658a4aeb8403f8e [formerly 5599e859e906704ab0d6b0a65658a4aeb8403f8e [formerly 843382a22560623c415f2e527be2a1bb1bb87772]]]]]
Former-commit-id: 75969df6de5f2c3ee08f81dc1a4d457d492b87ed [formerly 592aadc955cf333a8e23f7b75707159ed9510d8a]
Former-commit-id: 94cebea834834afcb565978fd8a188af8afa86a6
Former-commit-id: 8549165bda8f705454ee2f2dedc81276918c4b71
Former-commit-id: 0761f82c3eb56fded8c6f5c4ed4b4056625948e9
Former-commit-id: 74c23dae521058b04ea41ac90e9ba06f76ecd6d1 [formerly 3e7d2e15cc64a4ddb87f24d817a64c714a7f6c81]
Former-commit-id: e3a78bcbc38400fd94f9cc0dcf7cd4517000baa4
2017-12-28 10:17:45 +01:00
app Use default-extensions in cabal 2016-10-09 20:54:08 +02:00
bin Maj linux binary 2016-11-26 17:33:24 +01:00
src fix typo in debug log in the HTTP proxy 2017-12-28 10:17:45 +01:00
test ground 0 2016-05-11 23:39:02 +02:00
.dockerignore Add travis 2017-12-05 12:32:35 +01:00
.gitignore ground 0 2016-05-11 23:39:02 +02:00
.travis.yml Add travis 2017-12-05 12:32:35 +01:00
Dockerfile Update Dockerfile 2017-12-08 12:29:05 +01:00
LICENSE ground 0 2016-05-11 23:39:02 +02:00
logo_wstunnel.png Maj logo 2016-08-26 20:57:10 +02:00
README.md Update README.md 2017-08-24 13:26:43 +02:00
Setup.hs ground 0 2016-05-11 23:39:02 +02:00
stack.yaml Update docker file to use multistage build 2017-10-22 16:24:27 +02:00
wstunnel.cabal Add travis 2017-12-05 12:32:35 +01:00

wstunnel logo

Description

Most of the time when you are using a public network, you are behind some kind of firewall or proxy. One of their purpose is to constrain you to only use certain kind of protocols. Nowadays, the most widespread protocol is http and is de facto allowed by third party equipment.

This tool understands this fact and uses the websocket protocol which is compatible with http in order to bypass firewalls and proxies. Wstunnel allows you to tunnel what ever traffic you want.

My inspiration came from this project but as I don't want to install npm and nodejs to use this tool, I remade it in Haskell and improved it.

What to expect:

  • Good error messages and debug informations
  • Static tunneling (TCP and UDP)
  • Dynamic tunneling (socks5 proxy)
  • Support for http proxy (when behind one)
  • Support for tls/https server (with embeded self signed certificate, see comment in the example section)
  • Standalone binary for linux x86_64 (so just cp it where you want)
  • Standalone archive for windows

Binaries

P.S: Please do not pay attention to Main.hs because as I hate to write command line code this file is crappy

Command line

Use the websockets protocol to tunnel {TCP,UDP} traffic
wsTunnelClient <---> wsTunnelServer <---> RemoteHost
Use secure connection (wss://) to bypass proxies

wstunnel [OPTIONS] ws[s]://wstunnelServer[:port]
Client options:
  -L --localToRemote=[BIND:]PORT:HOST:PORT  Listen on local and forwards
                                            traffic from remote
  -D --dynamicToRemote=[BIND:]PORT          Listen on local and dynamically
                                            (with socks5 proxy) forwards
                                            traffic from remote
  -u --udp                                  forward UDP traffic instead of
                                            TCP
  -p --httpProxy=USER:PASS@HOST:PORT        If set, will use this proxy to
                                            connect to the server
Server options:
     --server                               Start a server that will forward
                                            traffic for you
  -r --restrictTo=HOST:PORT                 Accept traffic to be forwarded
                                            only to this service
Common options:
  -v --verbose                              Print debug information
  -q --quiet                                Print only errors
  -h --help                                 Display help message
  -V --version                              Print version information

Examples

Simplest one

On your remote host, start the wstunnel's server by typing this command in your terminal

wstunnel --server ws://0.0.0.0:8080

This will create a websocket server listenning on any interface on port 8080. On the client side use this command to forwards traffic trought the websocket tunnel

wstunnel -D 8888 ws://myRemoteHost:8080

This command will create a sock5 server listenning only on loopback interface on port 8888 and will forwards traffic.

Ex: With firefox you can setup a proxy using this tunnel by settings in networking preferences 127.0.0.1:8888 and selecting socks5 proxy

When behind a corporate proxy

An other useful example is when you want to bypass an http proxy (a corporate proxy for example) The most reliable way to do it is to use wstunnel as described below

Start your wstunnel server with tls activated

wstunnel --server wss://0.0.0.0:443 -r 127.0.0.1:22

The server will listen on any interface on port 443 (https) and restrict traffic to be forwarded only to the ssh daemon.

Be aware that the server will use self signed certificate with weak cryptographic algorithm. It was made in order to add the least possible overhead while still being compliant with tls.

So do not rely on wstunnel to protect your privacy, if you want to do so, forwards only traffic that is already secure by design (ex: https)

Now on the client side start the client with

wstunnel -L 9999:127.0.0.1:22 -p mycorporateproxy:8080 wss://myRemoteHost:443

It will start a tcp server on port 9999 that will contact the corporate proxy, negociate a tls connection with the remote host and forward traffic to the ssh daemon on the remote host.

You can now access your server from your local machine on ssh by using

ssh -p 9999 login@127.0.0.1

How to Build

Install the stack tool https://docs.haskellstack.org/en/stable/README/ or if you are a believer

curl -sSL https://get.haskellstack.org/ | sh

and run those commands at the root of the project

stack init
stack install

TODO

  • Add sock5 proxy
  • Add better logging
  • Add better error handling
  • Add httpProxy authentification
  • Add Reverse tunnel
  • Add more tests for socks5 proxy