No description
Find a file
Erèbe - Romain Gerard 93e66a1751 Create build_raspbian.sh
Former-commit-id: 56001d8833bf76de17e03d86d74e4f8a66f2e4d5
Former-commit-id: 5e1b3ca1c190b0851f630c1af3d50bd1576d0811 [formerly 855827f16995531ecca6f69dad7805a16d385125] [formerly b9929eb300bf5cedee35d4242ff83c1be6f2d935 [formerly fe7c83d28a6bcd72965d94167561e35101ffa81e [formerly fe7c83d28a6bcd72965d94167561e35101ffa81e [formerly fe7c83d28a6bcd72965d94167561e35101ffa81e [formerly fe03a695ce9e214bc462bc23f61625e20c916b9f]]]]]
Former-commit-id: b76fce1ea240ba17893647dff7bcfc6f3bf24cc3 [formerly 1268d7bba784713d7e735cd2c26091f919ee1261]
Former-commit-id: aea824e4ec29e996e55d3751adc30431c91836f1
Former-commit-id: 8b22eb2ce02033b4faae558c201b759e9711949e
Former-commit-id: 0053714b56c5b5e8424b6935767cc7cfae38d8db
Former-commit-id: f185e4bc67c5b6de2cbce62948dc19aed792df27 [formerly 09e28fd4048edfec91bbabcae907985d28417287]
Former-commit-id: bc59cfea13c9037c3ae8c4cf1f2c6a8122d46084
2020-05-01 13:38:19 +02:00
.github/workflows Update build.yml 2020-01-07 19:28:20 +01:00
app Fix stdio support #39 2020-02-24 22:52:42 +01:00
src #41 Add logging info when new ip connect to the server 2020-04-26 14:56:14 +02:00
test Add tests 2020-02-24 20:57:42 +01:00
.dockerignore Add travis 2017-12-05 12:32:35 +01:00
.gitignore ground 0 2016-05-11 23:39:02 +02:00
build_aarch64.sh Update build_aarch64.sh 2020-05-01 13:09:57 +02:00
build_raspbian.sh Create build_raspbian.sh 2020-05-01 13:38:19 +02:00
default.nix New dockerfile 2019-10-24 18:20:35 +02:00
Dockerfile Deprecate nix dockerfile 2020-01-06 00:37:16 +01:00
Dockerfile.old Deprecate nix dockerfile 2020-01-06 00:37:16 +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 fixed two small errors (#31) 2019-10-31 11:29:38 +01:00
stack.yaml Update dependencies 2019-10-24 13:46:58 +02:00
wstunnel.cabal Add tests 2020-02-24 20:57:42 +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 embedded 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 listening on any interface on port 8080. On the client side use this command to forward traffic through the websocket tunnel

wstunnel -D 8888 ws://myRemoteHost:8080

This command will create a sock5 server listening on port 8888 of a loopback interface and will forward traffic.

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

As proxy command for SSH

You can specify stdio as source port on the client side if you wish to use wstunnel as part of a proxy command for ssh

ssh -o ProxyCommand="wstunnel -L stdio:%h:%p ws://localhost:8080" my-server

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 using 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.

Do not rely on wstunnel to protect your privacy, as it only forwards 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, negotiate a tls connection with the remote host and forward traffic to the ssh daemon on the remote host.

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

ssh -p 9999 login@127.0.0.1

Wireguard and wstunnel

https://kirill888.github.io/notes/wireguard-via-websocket/

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