![]() There is some discussion about adding a crypto API to Javascript which would enable noVNC to support this type of encryption. Javascript is not fast enough to do encryption/decryption fast enough to be usable for noVNC. noVNC does not support RFB/VNC encryption. When you pass -ssl PEM to x11vnc this enabled RFB/VNC encryption. There are several encryption methods supported such as TLS (security type 18), VeNCrypt (security type 19). The RFB protocol (Remote Frame Buffer) used in VNC has the ability to upgrade during the initialization to use an encrypted connection. The WebSocket protocol supports unencrypted connections (ws://) and SSL/TLS encrypted connections (wss://). websockify to x11vnc (VNC server) - direct TCP socket connection.noVNC (browser) to websockify - using WebSocket protocol.You are dealing with two different network connections each of which has separate encryption options: websockify is included in noVNC since most VNC servers do not yet support WebSocket clients, but websockify is a separate project. The only VNC server that currently supports direct WebSocket connections is this fork of libvncserver. If the VNC server supported WebSocket connections then websockify would not be needed. from a browser) to connect to raw TCP socket services (e.g. websockify is a generic proxy/bridge that allows WebSocket connections (e.g. ![]() NoVNC and websockify are actually separate projects: Else, how can I get noVNC and x11vnc working with SSL? If this does create a secure connection, please let me know. As of now, it does not seem like turning on noVNC's encrypt option does much if x11vnc's SSL must be turned off (the encrypt option makes noVNC use wss:// instead of ws://). I am most concerned about a secure connection. The encrypt option for noVNC seems to have no effect on connecting to the server (the results are the same whether it's on or off). I use websockify instead of noVNC's launch.sh to have more options such as -ssl-only. utils/websockify -ssl-only -cert= -web=./ 6080 localhost:5900 X11vnc -forever -shared -unixpw_cmd -ssl However, I'm more interested in the HTML5 based noVNC.īoth x11vnc and noVNC both run on the same machine, using the commands: I do realize that x11vnc does come packaged with a java based applet viewer. If I turn off SSL for x11vnc, the client is able to connect with no problem. SSL: accept_openssl: cookie from ssl_helper FAILED. Whenever I try to connect, I get the error "Unsupported Security Types: 19,18" from noVNC and "SSL: ssl_helper: exit case 2 (ssl_init failed) I am trying to use an SSL connection with x11vnc (VNC server) and noVNC (VNC client). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |