## noVNC: HTML5 VNC Client
+[](https://travis-ci.org/novnc/noVNC)
### Description
-noVNC is a VNC client implemented using HTML5 technologies,
-specifically Canvas and WebSocket (supports 'wss://' encryption).
+noVNC is a HTML5 VNC client that runs well in any modern browser including
+mobile browsers (iOS and Android).
+
+Many companies, projects and products have integrated noVNC including
+[Ganeti Web Manager](http://code.osuosl.org/projects/ganeti-webmgr),
+[OpenStack](http://www.openstack.org),
+[OpenNebula](http://opennebula.org/),
+[LibVNCServer](http://libvncserver.sourceforge.net), and
+[ThinLinc](https://cendio.com/thinlinc). See
+[the Projects and Companies wiki page](https://github.com/novnc/noVNC/wiki/Projects-and-companies-using-noVNC)
+for a more complete list with additional info and links.
+
+### News/help/contact
+
+Notable commits, announcements and news are posted to
+<a href="http://www.twitter.com/noVNC">@noVNC</a>.
+
+If you are a noVNC developer/integrator/user (or want to be) please join the
+<a href="https://groups.google.com/forum/?fromgroups#!forum/novnc">
+noVNC discussion group</a>.
+
+Bugs and feature requests can be submitted via
+[github issues](https://github.com/novnc/noVNC/issues).
+If you are looking for a place to start contributing to noVNC, a good place to
+start would be the issues that are marked as
+["patchwelcome"](https://github.com/novnc/noVNC/issues?labels=patchwelcome).
+
+If you want to show appreciation for noVNC you could donate to a great non-
+profits such as:
+[Compassion International](http://www.compassion.com/),
+[SIL](http://www.sil.org),
+[Habitat for Humanity](http://www.habitat.org),
+[Electronic Frontier Foundation](https://www.eff.org/),
+[Against Malaria Foundation](http://www.againstmalaria.com/),
+[Nothing But Nets](http://www.nothingbutnets.net/), etc.
+Please tweet <a href="http://www.twitter.com/noVNC">@noVNC</a> if you do.
+
+
+### Features
+
+* Supports all modern browsers including mobile (iOS, Android)
+* Supported VNC encodings: raw, copyrect, rre, hextile, tight, tightPNG
+* WebSocket SSL/TLS encryption (i.e. "wss://") support
+* 24-bit true color and 8 bit colour mapped
+* Supports desktop resize notification/pseudo-encoding
+* Local or remote cursor
+* Clipboard copy/paste
+* Clipping or scolling modes for large remote screens
+* Easy site integration and theming (3 example themes included)
+* Licensed under the [MPL 2.0](http://www.mozilla.org/MPL/2.0/)
-For browsers that do not have builtin WebSocket support, the project
-includes [web-socket-js](http://github.com/gimite/web-socket-js),
-a WebSocket emulator using Adobe Flash .
+### Screenshots
-In addition, [as3crypto](http://github.com/lyokato/as3crypto_patched)
-has been added to web-socket-js to implement WebSocket SSL/TLS
-encryption, i.e. the "wss://" URI scheme.
+Running in Chrome before and after connecting:
-Special thanks to [Sentry Data Systems](http://www.sentryds.com) for
-sponsoring ongoing development of this project (and for employing me).
+<img src="http://novnc.com/img/noVNC-5.png" width=400>
+<img src="http://novnc.com/img/noVNC-7.jpg" width=400>
-### Screenshots
+See more screenshots
+<a href="http://novnc.com/screenshots.html">here</a>.
-Running in Chrome before and after connecting:
-<img src="http://kanaka.github.com/noVNC/img/noVNC-1.jpg" width=400> <img src="http://kanaka.github.com/noVNC/img/noVNC-2.jpg" width=400>
+### Browser Requirements
+
+* Chrome 8, Firefox 4, Safari 6, Opera 12, IE 11, Edge 12, etc.
+
+* HTML5 Canvas, WebSockets and Typed Arrays
+
+* Fast Javascript Engine: this is not strictly a requirement, but without a
+ fast Javascript engine, noVNC might be painfully slow.
+
+* See the more detailed
+[browser compatibility wiki page](https://github.com/novnc/noVNC/wiki/Browser-support).
+
+
+### Server Requirements
+
+Unless you are using a VNC server with support for WebSockets connections (such
+as [x11vnc/libvncserver](http://libvncserver.sourceforge.net/),
+[QEMU](http://www.qemu.org/), or
+[MobileVNC](http://www.smartlab.at/mobilevnc/)), you need to use a
+WebSockets to TCP socket proxy. There is a python proxy included
+('websockify').
+
+
+### Quick Start
+
+* Use the launch script to start a mini-webserver and the WebSockets proxy
+ (websockify). The `--vnc` option is used to specify the location of a running
+ VNC server:
+
+ `./utils/launch.sh --vnc localhost:5901`
+
+* Point your browser to the cut-and-paste URL that is output by the launch
+ script. Enter a password if the VNC server has one configured. Hit the
+ Connect button and enjoy!
+
+
+### Other Pages
+
+* [Modules/API](https://github.com/novnc/noVNC/wiki/Modules-API) - The library
+ modules and their Javascript API.
-See more screenshots <a href="http://kanaka.github.com/noVNC/screenshots.html">here</a>.
+* [Integration](https://github.com/novnc/noVNC/wiki/Integration) - Get noVNC
+ to work in existing projects.
+* [Troubleshooting](https://github.com/novnc/noVNC/wiki/Troubleshooting) - How
+ to troubleshoot problems.
-### Requirements
+* [Encrypted Connections](https://github.com/novnc/websockify/wiki/Encrypted-Connections) -
+ Setup websockify so that you can use encrypted connections from noVNC.
-Until there is VNC server support for WebSocket connections, you need
-to use a WebSocket to TCP socket proxy. There is a python proxy
-included ('wsproxy'). One advantage of using the proxy is that it has
-builtin support for SSL/TLS encryption (i.e. "wss://").
+* [Advanced Usage](https://github.com/novnc/noVNC/wiki/Advanced-usage) -
+ Generating an SSL certificate, starting a VNC server, advanced websockify
+ usage, etc.
-There a few reasons why a proxy is required:
+* [Testing](https://github.com/novnc/noVNC/wiki/Testing) - Run and write
+ tests.
- 1. WebSocket is not a pure socket protocol. There is an initial HTTP
- like handshake to allow easy hand-off by web servers and allow
- some origin policy exchange. Also, each WebSocket frame begins
- with 0 ('\x00') and ends with 255 ('\xff').
-
- 2. Javascript itself does not have the ability to handle pure byte
- strings (Unicode encoding messes with it) even though you can
- read them with WebSocket. The python proxy encodes the data so
- that the Javascript client can base64 decode the data into an
- array.
-
- 3. When using the web-socket-js as a fallback, WebSocket 'onmessage'
- events may arrive out of order. In order to compensate for this
- the client asks the proxy (using the initial query string) to add
- sequence numbers to each packet.
+* [Translations](https://github.com/novnc/noVNC/wiki/Translations) - Add and
+ modify localization for JavaScript and HTML.
-### Usage
-
-* To encrypt the traffic using the WebSocket 'wss://' URI scheme you
- need to generate a certificate for the proxy to load. You can generate
- a self-signed certificate using openssl. The common name should be the
- hostname of the server where the proxy will be running:
+### Authors/Contributors
- `openssl req -new -x509 -days 365 -nodes -out self.pem -keyout self.pem`
-
-* run a VNC server.
-
- `vncserver :1`
-
-* run the python proxy:
-
- `./utils/wsproxy.py -f source_port target_addr:target_port
-
- `./utils/wsproxy.py -f 8787 localhost:5901`
-
-
-* run the mini python web server to serve the directory:
-
- `./utils/web.py PORT`
-
- `./utils/web.py 8080`
-
-* Point your web browser at http://localhost:8080/vnc.html
- (or whatever port you used above to run the web server).
-
-* Specify the host and port where the proxy is running and the
- password that the vnc server is using (if any). Hit the Connect
- button and enjoy!
+* Core team:
+ * [Joel Martin](https://github.com/kanaka)
+ * [Samuel Mannehed](https://github.com/samhed) (Cendio)
+ * [Peter Åstrand](https://github.com/astrand) (Cendio)
+ * [Solly Ross](https://github.com/DirectXMan12) (Red Hat / OpenStack)
+ * [Pierre Ossman](https://github.com/CendioOssman) (Cendio)
+* Notable contributions:
+ * UI and Icons : Pierre Ossman, Chris Gordon
+ * Original Logo : Michael Sersen
+ * tight encoding : Michael Tinglof (Mercuri.ca)
-### Browser Support
-
-In the following table Jaunty is Ubuntu 9.04 and WinXP is Windows XP.
+* Included libraries:
+ * as3crypto : Henri Torgemane (code.google.com/p/as3crypto)
+ * base64 : Martijn Pieters (Digital Creations 2), Samuel Sieb (sieb.net)
+ * DES : Dave Zimmerman (Widget Workshop), Jef Poskanzer (ACME Labs)
+ * Pako : Vitaly Puzrin (https://github.com/nodeca/pako)
-#### Linux (Ubuntu 9.04)
-
-<table>
- <tr>
- <th>OS</th> <th>Browser</th>
- <th>Status</th>
- <th>Notes</th>
- </tr> <tr>
- <td>Jaunty</td> <td>Chrome 5.0.375.29</td>
- <td>Excellent</td>
- <td>Very fast. Native WebSockets.</td>
- </tr> <tr>
- <td>Jaunty</td> <td>Firefox 3.5</td>
- <td>Good</td>
- <td>Large full-color images are somewhat slow from web-socket-js overhead.</td>
- </tr> <tr>
- <td>Jaunty</td> <td>Opera 10.60</td>
- <td>Poor</td>
- <td>web-socket-js problems, mouse/keyboard issues. See note 1</td>
- </tr> <tr>
- <td>Jaunty</td> <td>Arora 0.5</td>
- <td>Good</td>
- <td>Broken putImageData so large full-color images
- are slow. Uses web-socket-js.</td>
- </tr> <tr>
- <td>Jaunty</td> <td>Konqueror 4.2.2</td>
- <td><strong>Broken</strong></td>
- <td>web-socket-js never loads</td>
- </tr> <tr>
- <td></td>
- <td></td>
- <td></td>
- <td></td>
- </tr> <tr>
- <td>WinXP</td> <td>Chrome 5.0.375.99</td>
- <td>Excellent</td>
- <td>Very fast. Native WebSockets.</td>
- </tr> <tr>
- <td>WinXP</td> <td>Firefox 3.0.19</td>
- <td>Good</td>
- <td>Some overhead from web-socket-js.</td>
- </tr> <tr>
- <td>WinXP</td> <td>Safari 5.0</td>
- <td>Fair</td>
- <td>Fast. Native WebSockets. Broken 'wss://' (SSL) - weird client header</td>
- </tr> <tr>
- <td>WinXP</td> <td>IE 6, 7, 8</td>
- <td><strong>Non-starter</strong></td>
- <td>No basic Canvas support. Javascript painfully slow.</td>
- </tr>
-</table>
-
-
-* Note 1: Opera interacts poorly with web-socket-js. After two
- disconnects the browser tab or Flash often hang. Although Javascript
- is faster than Firefox 3.5, the high variability of web-socket-js
- performance results in overall performance being lower. Middle mouse
- clicks and keyboard events need some work to work properly under
- Opera.
-
-
-### Integration
-
-The client is designed to be easily integrated with existing web
-structure and style.
-
-At a minimum you must include the `vnc.js` and `default_controls.js`
-scripts and call their load() functions. For example:
-
- <head>
- <script src='include/vnc.js'></script>
- <script src="include/default_controls.js"></script>
- </head>
- <body>
- <div id='vnc'>Loading</div>
- </body>
- <script>
- window.onload = function () {
- DefaultControls.load('vnc');
- RFB.load(); };
- </script>
-
-See `vnc.html` and `vnc_auto.html` for examples. The file
-`include/plain.css` has a list of stylable elements.
-
-The `vnc.js` also includes other scripts within the `include`
-sub-directory. The `VNC_uri_prefix` variable can be use override the
-URL path to the directory that contains the `include` sub-directory.
-
-
-### Troubleshooting
-
-You will need console logging support in the browser. Recent Chrome
-and Opera versions have built in support. Firefox has a nice extension
-called "firebug" that gives console logging support.
-
-First, load the noVNC page with `logging=debug` added to the query string.
-For example `vnc.html?logging=debug`.
-
-Then, activate the console logger in your browser. With Chrome it can
-be activate using Ctrl+Shift+J and then switching to the "Console"
-tab. With firefox+firebug, it can be activated using Ctrl+F12.
-
-Now reproduce the problem. The console log output will give more
-information about what is going wrong and where in the code the
-problem is located. If you file a issue/bug, it can be very helpful to
-copy the last page of console output leading up the problem into the
-issue report.
+* [Contribution guide](https://github.com/novnc/noVNC/wiki/Contributing)
projects / mirror_novnc.git / blobdiff