Bug 383870 - KRDC cannot connect to VNC server with RFB version 3.8
Summary: KRDC cannot connect to VNC server with RFB version 3.8
Status: RESOLVED UPSTREAM
Alias: None
Product: krdc
Classification: Applications
Component: VNC (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-22 19:40 UTC by Raf
Modified: 2017-08-29 19:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raf 2017-08-22 19:40:19 UTC
KRDC version 16.08.2
KDE Plasma 5.8.6
KDE frameworks: 5.26.0
Qt version: 5.6.1
OS: OpenSUSE LEAP 42.2
libvncserver0-0.9.9-13.4

I cannot connect to my VNC server (Windows10, Tiger VNC for Win64 1.7.0) using KRDC. When I try to connect I can see only blue screen with permanent "connecting" status in the window. The output from the terminal is only:

KRDC: 1687 871
KRDC: rfbInitClient failed

The output from the Tiger VNC Server log: 

# Wrong connection with Anonymous TLS 
Tue Aug 22 20:15:38 2017
 SocketManager: accepting incoming connection
 TcpSocket:   ACCEPT xxx.xxx.xxx.xxx
 Connections: accepted: xxx.xxx.xxx.xxx::xxxx
 SConnection: reading protocol version
 SConnection: Client needs protocol version 3.8
 SConnection: processing security type message
 SConnection: Client requests security type VeNCrypt(19)
 SConnection: processing security message
 SConnection: processing security message
 SConnection: processing security message
 SConnection: processing security message
 SVeNCrypt:   Client requests security type TLSVnc (258)
 TLS:         Process security message (session 0000000000000000)
 TLS:         Anonymous session has been set
 TLS:         Deferring completion of TLS handshake: Resource temporarily
              unavailable, try again.

Tue Aug 22 20:15:39 2017
 SConnection: processing security message
 TLS:         Process security message (session 0000000001798FA0)
 TLS:         TLS Handshake failed: Could not negotiate a supported cipher
              suite.
 TLS:         TLS session wasn't terminated gracefully
 SConnection: AuthFailureException: TLS Handshake failed
 Connections: closed: xxx.xxx.xxx.xxx::xxxx (TLS Handshake failed)
 EncodeManager: Framebuffer updates: 0
 EncodeManager:   Total: 0 rects, 0 pixels
 EncodeManager:          0 B (1:-1.#IND ratio)

---

# Wrong connection without TLS
Tue Aug 22 20:31:09 2017
 SocketManager: accepting incoming connection
 TcpSocket:   ACCEPT xxx.xxx.xxx.xxx
 Connections: accepted: xxx.xxx.xxx.xxx::xxxxx
 SConnection: reading protocol version
 SConnection: Client needs protocol version 3.8
 SConnection: processing security type message
 SConnection: Client requests security type VeNCrypt(19)
 SConnection: processing security message
 SConnection: processing security message
 SConnection: processing security message
 Connections: closed: 192.168.1.13::55352 (Clean disconnection)
 EncodeManager: Framebuffer updates: 0
 EncodeManager:   Total: 0 rects, 0 pixels
 EncodeManager:          0 B (1:-1.#IND ratio)

----

When I use TigerVNC Viewer v1.6.0 on Linux everything works fine and I am able to connect to my VNC server.

Also when I changed VNC server config and force it to use RFB version 3.3 everything works fine and KRDC is able to connect to the server.

Maybe this is libvncserver issue ?
Comment 1 Urs Wolfer 2017-08-24 18:16:23 UTC
Yes, this should be reported against libvncserver. Please post the link here after reporting it.
Comment 2 Raf 2017-08-29 19:05:41 UTC
Tested also with Remmina with similar results. So it looks like this is problem with libvncclient.

Also I found this which looks similar: https://bugs.kde.org/show_bug.cgi?id=369545

Looks like it is fixed in version 0.9.11, but I didn't test it by myself.