Additional information:
It seems that the bug is on the Xvnc-Server side. I looked at the ethernet traffic
while the authentication happed with the Ethereal-Tool.
The following error occurs during the connection procedure:
1. The connection is build up correctly and the version numbers are exchanged
2. Then the authentication-request-value (4 bytes 0x00000002) and the
challange-bytes(16 bytes) were send from the server to the client.
3. This sequence is read correctly by the client who now sends back the encrypted
password (16 bytes)
4. And now the bug happends!
The client waits for the authentication result and tryes to read 4 bytes from
the server who should return 0x00000000.
Before the server has checked the password, he sends sporadically one byte
containing the value 0x02 over the opened socket to the client.
The client read this byte assuming its one byte of the 4 byte authentication
result. So after the server has send the success of the
authentication (4 bytes)
the client reads the rest oft the corrupted result and complaints for the
unknown result.
So the values of this result may consist
in 0x02000000 ( dec. 33554432 I mostly observed this one)
or 0x02020000 ( dec. 33685504 )
or 0x02020200 ( dec. 33686016 )
or 0x02020202 ( dec. 33686018 )
In the record file of the Ethereal-Tool I detected, that even after (!) the
authentication answer the server still sends sporadically the disturbing
0x02-byte!
I think its a real serious bug on the server side. It might have to do with the poor
performance of the server ?
(in my case an old pentium box with 166MHz, linux debian kernel 2.4.20, Xvnc version
3.3.7 - built Jul 18 2003)
Is there anyone concerned with the VNC development who can check the server routines
to fix the bug ?
Waiting for feedback,
Bernd M|ller
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
