x11vnc // TigerVnc -> No valid VeNCrypt sub-type

[b1r0n3r]

Hi Guys, I am having issues getting TigerVNC to display my Toon(1)
Am running: "You are currently running version 4.22.7 on a qb2 with flavour uni"
Have installed x11vnc_0.9.13-r3_qb2.ipk (but also tried x11vnc_0.9.13-r0_qb2.ipk)
all to no avail.
When connecting with Tiger VNC, all I get is the error from the screenshot "Authentication failure: No valid VeNCrypt sub-type"

x11vnc.png (67.21 KiB) Viewed 7755 times

After removing, rebooting and installing, I would expect x11vnc to request a new password, but there is none of that - it just starts the VNC service on port 5900. and the result with TigerVNC is the same.

Code: Select all

eneco-001-029353:~# ps w |grep [x]11vnc
 1666 root     11472 S    /usr/bin/x11vnc-bin -shared -forever -rawfb map:/dev/fb0@800x480x32 -pipeinput UINPUT:touch,touch_always=
 1721 root         0 Z    [x11vnc-bin]

How to get this working again.....?

[edit]
Running x11vnc manually lets me see a bit more, and when connecting from TigerVNC, the following is shown:

Code: Select all

The SSL VNC desktop is:  eneco-001-029353:0
PORT=5900
SSLPORT=5900
13/02/2019 13:05:26 SSL: accept_openssl(OPENSSL_VNC)
13/02/2019 13:05:26 accept_openssl: using socketpair: 10 11
13/02/2019 13:05:26 SSL: spawning helper process to handle: 192.168.1.15:59018
13/02/2019 13:05:26 SSL: helper for peerport 59018 is pid 20296:
13/02/2019 13:05:28 check_vnc_tls_mode: waited: 1.427076 / 1.40 input: (future) RFB Handshake
13/02/2019 13:05:28 check_vnc_tls_mode: version: 3.8
13/02/2019 13:05:28 check_vnc_tls_mode: reply: 19 (VeNCrypt)
13/02/2019 13:05:28 vencrypt: received 0.2 client version.
13/02/2019 13:05:28 SSL: ssl_helper[20296]: exit case 2 (ssl_init failed)
13/02/2019 13:05:28 SSL: accept_openssl: cookie from ssl_helper[20296] FAILED. 0

Thanks!!

[JackV]

maybe a little late but I think I found a solution.
I used to start x11vnc on my Toon 1 with /usr/bin/x11vnc
TigerVNC stopped working with messages like :
- no matching security types
- No valid VeNCrypt sub-type
bVNC on Android still worked fine though.
When I looked for the process on my toon I found :
Toon1 ~> ps | grep x11vnc

10971 root 11592 S /usr/bin/x11vnc-bin -shared -forever -rawfb map:/dev/fb0@800x480x32 -pipeinput UINPUT:touch,touch_always=1,abs,pressure=128,tslib_cal=/etc/pointercal,direct_abs=/dev/input/event0,direct_btn=/dev/input/event0,direct_rel=/dev/input/event0,direct_key=/dev/input/event0,nouinput -cursor arrow -ssl SAVE -vencrypt nodh:plain:support -usepw -quiet -bg

I no longer use the command /usr/bin/x11vnc but almost the complete command I found above.
I took out '-ssl SAVE -vencrypt nodh:plain:support' and now I use :

/usr/bin/x11vnc-bin -shared -forever -rawfb map:/dev/fb0@800x480x32 -pipeinput UINPUT:touch,touch_always=1,abs,pressure=128,tslib_cal=/etc/pointercal,direct_abs=/dev/input/event0,direct_btn=/dev/input/event0,direct_rel=/dev/input/event0,direct_key=/dev/input/event0,nouinput -cursor arrow -usepw -quiet -bg

I can now connect with TigerVNC from both Linux and Windows and bVNC also still works.