websockify/utils
Joel Martin 0f7f146f20 utils/launch.sh: find top web dir (with vnc.html). 2010-12-21 10:17:43 -06:00
..
Makefile wswrapper: wrap existing server using LD_PRELOAD. 2010-12-02 22:11:02 -06:00
README.md First pass at wsproxy using node (node.js). 2010-11-07 19:06:20 -06:00
launch.sh utils/launch.sh: find top web dir (with vnc.html). 2010-12-21 10:17:43 -06:00
md5.c Remove left over record code. Squelch compile warnings 2010-11-06 10:53:32 -05:00
md5.h Update C proxy to WS protocol version 76. 2010-06-30 20:39:41 -05:00
md5_test.c Update C proxy to WS protocol version 76. 2010-06-30 20:39:41 -05:00
web.py set socket option SO_REUSEADDR to prevent "Address already in use" error 2010-12-21 23:31:46 +08:00
websocket.c Add --key option for separate cert and key file. 2010-11-06 10:55:09 -05:00
websocket.h Add --key option for separate cert and key file. 2010-11-06 10:55:09 -05:00
websocket.py Add --key option for separate cert and key file. 2010-11-06 10:55:09 -05:00
wsproxy.c Add --key option for separate cert and key file. 2010-11-06 10:55:09 -05:00
wsproxy.js wsproxy.js: Fix multi-frame decoding. 2010-11-07 22:28:08 -06:00
wsproxy.py wsproxy: Fix --key parameter use. 2010-11-06 14:12:37 -05:00
wswrap wswrapper: fix preload path and interpose port. 2010-12-16 14:04:16 -06:00
wswrapper.c wswrapper: fix preload path and interpose port. 2010-12-16 14:04:16 -06:00

README.md

wsproxy: WebSockets to TCP Proxy

How it works

At the most basic level, wsproxy just translates WebSockets traffic to normal socket traffic. wsproxy accepts the WebSockets handshake, parses it, and then begins forwarding traffic between the client and the target in both directions. WebSockets payload data is UTF-8 encoded so in order to transport binary data it must use an encoding that can be encapsulated within UTF-8. wsproxy uses base64 to encode all traffic to and from the client. Also, WebSockets traffic starts with '\0' (0) and ends with '\xff' (255). Some buffering is done in case the data from the client is not a full WebSockets frame (i.e. does not end in 255).

Additional features

These are not necessary for the basic operation.

  • Daemonizing: When the -f option is not specified, wsproxy runs in the background as a daemon process.

  • SSL (the wss:// WebSockets URI): This is detected automatically by wsproxy by sniffing the first byte sent from the client and then wrapping the socket if the data starts with '\x16' or '\x80' (indicating SSL).

  • Flash security policy: wsproxy detects flash security policy requests (again by sniffing the first packet) and answers with an appropriate flash security policy response (and then closes the port). This means no separate flash security policy server is needed for supporting the flash WebSockets fallback emulator.

  • Session recording: This feature that allows recording of the traffic sent and received from the client to a file using the --record option.

Implementations

There are three implementations of wsproxy included: python, C, and Node (node.js).

Here is the feature support matrix for the wsproxy implementations:

Implementation Basic Proxying Multi-process Daemonizing SSL/wss Flash Policy Server Session Recording
python yes yes yes yes 1 yes yes
C yes yes yes yes yes no
Node (node.js) yes yes no no no no
  • Note 1: to use SSL/wss with python 2.5 or older, see the following section on Building the Python ssl module.

Building the Python ssl module (for python 2.5 and older)

  • Install the build dependencies. On Ubuntu use this command:

    sudo aptitude install python-dev bluetooth-dev

  • Download, build the ssl module and symlink to it:

    cd noVNC/utils

    wget http://pypi.python.org/packages/source/s/ssl/ssl-1.15.tar.gz

    tar xvzf ssl-1.15.tar.gz

    cd ssl-1.15

    make

    cd ../

    ln -sf ssl-1.15/build/lib.linux-*/ssl ssl