Bug 289135 - krdc doesn't connect to VNC servers when it uses libvncserver 0.9.8
Summary: krdc doesn't connect to VNC servers when it uses libvncserver 0.9.8
Status: RESOLVED UPSTREAM
Alias: None
Product: krdc
Classification: Applications
Component: VNC (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-16 18:34 UTC by Jakub Schmidtke
Modified: 2011-12-29 18:53 UTC (History)
3 users (show)

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 Jakub Schmidtke 2011-12-16 18:34:22 UTC
Version:           unspecified (using Devel) 
OS:                Linux

krdc is unable to connect to VNC servers after updating libvncserver from 0.9.7 to 0.9.8 or 0.9.8.1.

When I inspect the traffic using wireshark, it looks like it is unable to authenticate.

This doesn't work:
kdenetwork-krdc 4.7.90
libvncserver 0.9.8

I also tried 0.9.8.1 and it also doesn't work.

This does:
kdenetwork-krdc 4.7.90
libvncserver 0.9.7

When it works (with 0.9.7) the wireshark shows following data:
(S = Server, C = Client):
S->C: Server protocol version: 003.889
C->S: Client protocol version: 003.008
S->C: Number of security types: 3
      Security type: Unknown (30)
      Security type: VNC (2)
      Security type: Unknown (35)
C->S: Security type selected: VNC (2)
S->C: Authentication challenge: 3a9c(...)
C->S: Authentication response: 8aa5(...)
S->C: .... .... .... .... .... .... .... ...0 = Authentication result: OK

And the rest of the VNC session continues.

With 0.9.8.1 it shows:

S->C: Server protocol version: 003.889
C->S: Client protocol version: 003.008
S->C: Number of security types: 3
      Security type: Unknown (30)
      Security type: VNC (2)
      Security type: Unknown (35)
C->S: Security type selected: Unknown (30)
S->C: Security type selected: Invalid (0)

And the client closes the connection. Also, the KRDC could show something, an error message, or at least a message saying that the connection was closed. Instead it just sits there doing nothing, so there is no way to tell whether it's just waiting to connect, or that something failed...


Reproducible: Always

Steps to Reproduce:
Install krdc and libvncserver 0.9.8 or 0.9.8.1 and try connecting to a VNC server...

Actual Results:  
It doesn't connect

Expected Results:  
It connects

OS: Linux (x86_64) release 3.1.5-1-ARCH
Compiler: gcc
Comment 1 Urs Wolfer 2011-12-28 07:52:35 UTC
I'm using Archlinux with libvncserver 0.9.8.1-1 and KRDC 4.7.4-1. I do not have any issue with connecting to a VNC server here. Probably you have a problem with one specific VNC server? What VNC server are you using? Can you try with another one?
Comment 2 Jakub Schmidtke 2011-12-29 10:37:09 UTC
It's a vnc server on a MacOs machine. I don't have access to my Linux box at the moment so I can't run any experiments till I get it back (in about 10 days).
Comment 3 Andrea Scarpino 2011-12-29 15:46:41 UTC
"LibVNCServer 0.9.8.2 released!
This is a maintenance release that fixes a regression in libvncclient that crept in with Apple Remote Desktop support added with 0.9.8. Viewers that were not adapted to the new functionality would fail connecting to ARD servers before."

Probably this is fixed in the last libvncserver version. Isn't related to kdrc then.
Comment 4 Urs Wolfer 2011-12-29 18:53:02 UTC
Thanks Andrea for investigating. I think that must be the issue here. Closing as upstream bug.