[Bug 267023] New: vncviewer does not work w/ older vncserver (esp. sles9)
https://bugzilla.novell.com/show_bug.cgi?id=267023 Summary: vncviewer does not work w/ older vncserver (esp. sles9) Product: openSUSE 10.3 Version: Alpha 3 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: max@novell.com ReportedBy: svollath@novell.com QAContact: sndirsch@novell.com I can't do a vncviewer connection to sles9 anymore w/ 10.3. ***** $ vncviewer <host>:1 Connected to RFB server, using protocol version 3.7 ***** .. but sles9 and sles10 using version 3.3. So it is not possible from e.g. openSUSE 10.3 to connect to a sles9 installation or system, which is a bad idea since r&d uses latest/stable on the desktop. sles10 uses protocol version 3.3 too, but somehow that works with latest vncviewer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |svollath@novell.com ------- Comment #1 from max@novell.com 2007-04-23 06:54 MST ------- In which way does it fail and why do you think that the protocol version is the reason? On which hardware architectures does it happen? AFAIK both ends of a VNC connection are supposed to fall back, if the other end only supports a lower protocol version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 svollath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|svollath@novell.com | ------- Comment #2 from svollath@novell.com 2007-04-23 07:26 MST ------- ***** $ vncviewer <host>:1 Connected to RFB server, using protocol version 3.7 ***** Nothing happens after this output/no password is asked for/no vncviewer window comes up. Tested "vnc installations" and "remote administration". All servers were accessable from SL10.0 and SLES9/10. Hardware=All, so perhaps it happens on all? I reproduced it on i386 (sles9 servers) x86_64 (sles9 servers) ppc (10.3 clients) i386 (10.3 clients) So there might be the need to set up some machines and enable debug logging ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |svollath@novell.com ------- Comment #3 from max@novell.com 2007-04-23 08:14 MST ------- Do you have a SLES9 installation at hand that I could use as the server side for some tests? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #6 from max@novell.com 2007-04-24 09:29 MST ------- As part of the initial handshake of a VNC connection, the server sends the highest version of the RFB protocol it is able to support to the client. The client then sends back the version number to be used for the connection, which has to be smaller than or equal to the version reported by the server. The problem is, that the Xvnc server we have on SLES9, which comes from the XF4VNC project, uses an inofficial protocol version number (3.130), which is higher than all official ones (3.3, 3.7, and 3.8). With our vncviewer versions up to openSUSE 10.2 this wasn't a problem, because they were falling back to version 3.3 as the highest version they understand themselves, which was also understood by the server. Now the latest release of tightvnc supports version 3.7 of the RFB protocol and according to the rules of RFB protocol versioning it can expect the server to support that as well, because it was reporting a much higher version number. I see two possible solutions to this: 1. Releasing an update for SLES9 that stops Xvnc from reporting an illegal protocol version. This would effectively also disable the extensions to the protocol it supports under the inofficial version, but AFAICS none of our viewers ever supported these anyways, so it should be safe. 2. Add a workaround to our current vncviewer, so that it falls back to version 3.3 instead of 3.7, if the server reports version 3.130. This would fix things for people using vncviewer from 10.3 or newer, but the non-standard Xvnc on SLES9 would still be there and affect people using newer VNC viewers from other distros or other OSes. So, I think 1. would be the cleanest solution, but it might make sense to implement both, so that it is also possible to make VNC connections from 10.3 to unpatched SLES9 installations and to non-SUSE installations of XF4VNC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |ast@novell.com ------- Comment #7 from max@novell.com 2007-04-24 09:49 MST ------- Implemented 2. and submitted to STABLE. Anja, I think we should do 1. as well, at least as an optional update to which we can point customers, who e.g. have problems connecting to SLES9 via VNC from Windows machines. The change itself is trivial, just changing a define line in a header file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 ------- Comment #8 from sndirsch@novell.com 2007-04-24 10:26 MST -------
1. Releasing an update for SLES9 that stops Xvnc from reporting an illegal protocol version. This would effectively also disable the extensions to the protocol it supports under the inofficial version, but AFAICS none of our viewers ever supported these anyways, so it should be safe. Well, at least the xf4vncviewer on SLES9 did, but probably nobody ever used it, especially the additional features.
Indeed the patch would be trivial: --- include/rfbproto.h.orig 2007-04-24 18:16:53.133527286 +0200 +++ include/rfbproto.h 2007-04-24 18:17:32.258198059 +0200 @@ -181,7 +181,7 @@ #define rfbProtocolVersionFormat "RFB %03d.%03d\n" #define rfbProtocolMajorVersion 3 -#define rfbProtocolMinorVersion 130 +#define rfbProtocolMinorVersion 3 #define rfbProtocolFallbackMinorVersion 3 typedef char rfbProtocolVersionMsg[13]; /* allow extra byte for null */ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 ------- Comment #11 from sndirsch@novell.com 2007-04-28 05:19 MST ------- Not sure, why this is now set to NEEDINFO(svollath). Could you explain, Reinhard? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 ------- Comment #14 from sndirsch@novell.com 2007-05-12 10:16 MST ------- Harald? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 hmuelle@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|max@novell.com |sndirsch@novell.com Status|ASSIGNED |NEW ------- Comment #16 from hmuelle@novell.com 2007-05-14 02:53 MST ------- WHY was this assigned to me? Do not assign this to "maintenance" for asking about doing a fix: http://fourier.suse.de/mlarch/SuSE/devel/2007/devel.2007.03/msg00001.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 ------- Comment #17 from sndirsch@novell.com 2007-05-14 02:59 MST ------- The fix is a one-liner. It will make features, which are provided by rfbProtocolMinorVersion 130, no longer usable, so it can affect customers, which are using the xf4vnviewer. I'm not sure if there are any customers, which use xf4vncviewer and the features of the rfbProtocolMinorVersion 130. So potentially there is a risk. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #18 from sndirsch@novell.com 2007-05-14 03:02 MST ------- I propose to implement option 1 (see Reinhard's comment #6) only when we get any customer complains. Closing as fixed for now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED Priority|P5 - None |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267023 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #21 from sndirsch@novell.com 2007-05-14 11:08 MST ------- fixed for SLES9-SP4. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com