FS#27595 - [kdenetwork-krdc] connection problem after libvncserver update
Attached to Project:
Arch Linux
Opened by Jakub Schmidtke (sjakub) - Friday, 16 December 2011, 18:30 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 30 December 2011, 04:17 GMT
Opened by Jakub Schmidtke (sjakub) - Friday, 16 December 2011, 18:30 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 30 December 2011, 04:17 GMT
|
Details
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-1 libvncserver 0.9.8-4 I also tried 0.9.8.1-1 and it also doesn't work. This does: kdenetwork-krdc 4.7.90-1 libvncserver 0.9.7-3 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. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Friday, 30 December 2011, 04:17 GMT
Reason for closing: Fixed
Additional comments about closing: libvncserver 0.9.8.2-1
Friday, 30 December 2011, 04:17 GMT
Reason for closing: Fixed
Additional comments about closing: libvncserver 0.9.8.2-1
Comment by
Jakub Schmidtke (sjakub) - Friday,
16 December 2011, 18:34 GMT
Comment by Andrea Scarpino (BaSh) -
Thursday, 29 December 2011, 15:47 GMT
I also created a bug report upstream:
https://bugs.kde.org/show_bug.cgi?id=289135
, just in case :)
libvncserver 0.9.8.2 should fix this, please try it and let we
know.