Go to file
Joel Martin 6d1e216115 fork noVNC, rename to websockify, cleanup.
Split of wsproxy from noVNC and rename it websockify.
2011-01-12 18:09:54 -06:00
docs fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
include fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
other fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
tests fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
.gitignore fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
LICENSE.txt fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
Makefile fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
README.md fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
rebind fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
rebind.c fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
websocket.py fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
websockify fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00
wstelnet.html fork noVNC, rename to websockify, cleanup. 2011-01-12 18:09:54 -06:00

README.md

websockify: WebSockets support for any application/server

websockify was formerly named wsproxy and was part of the noVNC project.

At the most basic level, websockify just translates WebSockets traffic to normal socket traffic. websockify 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. websockify 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 websockify features

These are not necessary for the basic operation.

  • Daemonizing: When the -D option is specified, websockify runs in the background as a daemon process.

  • SSL (the wss:// WebSockets URI): This is detected automatically by websockify 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: websockify 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.

  • Mini-webserver: websockify can detect and respond to normal web requests on the same port as the WebSockets proxy and Flash security policy. This functionality is activate with the --web DIR option where DIR is the root of the web directory to serve.

  • Wrap a program: see the "Wrap a Program" section below.

Implementations of websockify

The primary implementation of websockify is in python. There are two other implementations of websockify in C, and Node (node.js) in the other directory.

Here is the feature support matrix for the the websockify implementations:

Program Language Multiprocess Daemonize SSL/wss Flash Policy Server Session Record Web Server Program Wrap
websockify python yes yes yes 1 yes yes yes yes
other/websockify C yes yes yes yes no no no
other/websockify.js Node (node.js) yes no no 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.

Wrap a Program

In addition to proxying from a source address to a target address (which may be on a different system), websockify has the ability to launch a program on the local system and proxy WebSockets traffic to a normal TCP port owned/bound by the program.

The is accomplished with a small LD_PRELOAD library (rebind.so) which intercepts bind() system calls by the program. The specified port is moved to a new localhost/loopback free high port. websockify then proxies WebSockets traffic directed to the original port to the new (moved) port of the program.

The program wrap mode is invoked by replacing the target with -- followed by the program command line to wrap.

`./websockify 2023 -- PROGRAM ARGS`

The --wrap-mode option can be used to indicate what action to take when the wrapped program exits or daemonizes.

Here is an example of using websockify to wrap the vncserver command (which backgrounds itself) for use with noVNC:

`./websockify 5901 --wrap-mode=ignore -- vncserver -geometry 1024x768 :1`

Here is an example of wrapping telnetd (from krb5-telnetd).telnetd exits after the connection closes so the wrap mode is set to respawn the command:

`sudo ./websockify 2023 --wrap-mode=respawn -- telnetd -debug 2023`

The wstelnet.html page demonstrates a simple WebSockets based telnet client.

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 websockify/

    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