Hello,
I'm trying to use ssvnc in Windows 7, as I use it normally from Debian. I've tried both ssvnc_windows_only-1.0.29.zip and also ssvnc_windows_only-1.0.29.zip. After extraction, from the command prompt (cmd), either with "run as administrator" or not, when I run ssvnc,exe with -ssl or by selecting SSL radio button.
So with "SSL" radio button selected and click the button "Connect", another little window opens saying "Connecting to 127.0.0.1:30 - Status: Connection established.".
Then I always get this error of TighVNC with a message box with only an "OK" button with a yellow triangular signal with an exclamation point inside saying "ReadExact: Socket error while reading" (image attached).
If I disable SSL in the x11vnc server and try from windows 7 to run ssvnc.exe, without -ssl option and with "None" radio button selected and click the button "Connect", another little window opens saying "Connecting..." and then a big window opens with the vnc session from the x11vnc server. So, apparently, this problem is only with the -ssl option.
When using the -ssl option or the SSL Button selected I've watched for x11vnc log file: the main part of the x11vnc log is the following:
30/03/2016 14:24:42 connect_tcp: trying: 127.0.0.1 20000
30/03/2016 14:24:42 SSL: ssl_init[10825]: 8/8 initialization timeout: 20 secs.
30/03/2016 14:24:42 SSL: ssl_helper[10825]: SSL_accept() *FATAL: -1 SSL FAILED
30/03/2016 14:24:42 SSL: error:14076102:SSL routines:SSL23_GET_CLIENT_HELLO:unsupported protocol
30/03/2016 14:24:42 SSL: ssl_helper[10825]: Proto: nosession
30/03/2016 14:24:42 SSL: accept_openssl: cookie from ssl_helper[10825] FAILED. 0
In x11vnc I only use "-ssl -sslonly" options.
I have no problems connecting to the x11vnc server running those ssl options with ssvnc with ssl from either Debian 7 or 8 using the ssvnc package from the repositories, nor from bvnc android application. Both connect and work very well with the x11vnc server from debian 8 repositories.
I enjoy ssvnc in Debian linux and I would like to enjoy it from Windows 7 also. Please help. Ssvnc is very usefull to have secured vnc connections without using a ssh server. Thank you for your work.
Hi again,
I've managed to get x11vnc to work with ssvnc in debian and bvnc on android using the x11vnc options of "-ssl TMP ..." or, alternatively, "-ssl SAVE ...". ssvnc on debian and bvnc android clients continued to work fine, but not ssvnc in Windows distributed here... I always get the error posted above.
The workaround to not depend on a RDP server instead of x11vnc on my Debian VNC over SSL server was to use TigerVNC, install it in Windows, and use the selected options in the image attached to connecto to "x11vnc -ssl TMP ..." or "x11vnc -ssl SAVE ...".
Now I use x11vnc and ssvnc in Debian, bnvc on android and TigerVNC on windows to connect to my x11vnc VNC over SSL server session of my debian headless bananapi.