today i sniffed the traffic and compared the handshake from tsclient and vinagre. the handshake from vinagre seems not to work as specified in the rfb protocol. see: http://datatracker.ietf.org/doc/draft-levine-rfb/
summarized protocol v.3.8 handshake: server tells highest protocol version on connection: "RFB 003.008\n" (hex 52 46 42 20 30 30 33 2e 30 30 38 0a) client tells it version, too: "RFB 003.008\n" (hex 52 46 42 20 30 30 33 2e 30 30 38 0a) but vinagres reply to the server is "RFB 003.008 " (hex 52 46 42 20 30 30 33 2e 30 30 38 00) the end of the string differs from vinagre (hex: 00) and tsclient (hex: 0a). v1.x servers of tightvnc just seem to take the rfb-string "RFB 003.008" without newline at the end. v2.x servers of tightvnc seem to read all of the reply, includeing the last character that's why, i guess, the server logs "Invalid format of the RFB version message" maybe thats the point. someone has to investigate this. tested on: lucid: tsclient: 0.150 vinagre: 2.30.2 winxp pro sp3: tightvnc-server 1.3.10 tightvnc-server 2.0.2 -- Vinage closes connection to tightvncserver 2.0 beta4 immediately https://bugs.launchpad.net/bugs/598597 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
