Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libvncserver 0.9.12 patch 8b06f83 broke the ConnectToRFBRepeater functionality. #348

Closed
KWBerry opened this issue Nov 20, 2019 · 3 comments

Comments

@KWBerry
Copy link

KWBerry commented Nov 20, 2019

It seems that the patch 8b06f83 has broken the VNC ConnectToRFBRepeater functionality.

Prior to updating my system to libvncserver version 0.9.12, which includes this patch, my VNC repeater configuration was working without problems. My setup used the perl code implementation of the UltraVNC repeater interface called ultravnc_repeater.pl by Karl J. Runge. Since upgrading libvncserver my setup no longer works. I have traced the problem to libvncserver is not sending exactly 250 byte during the repeater connection setup partion of the interface. I also reviewed the offical UltraVNC repeater code found on line 71 of
https://sourceforge.net/p/ultravnc/code/HEAD/tree/UltraVNC%20Project%20Root/UltraVNC/repeater/mode2_listener_server.cpp

Both sets of code are expecting exactly 250 bytes of characters during the establishment of the connection.

This patch attempts to prevent sending uninitialized data (an appropriate goal) by shorting the message sent to only the characters in the actual message (in my case to "ID:1234"), which breaks the interface design. The appropriate patch should have been to pad the message with null characters out the the full length of the buffer (250 bytes).

Thanks,

Kenneth Berry

@bk138
Copy link
Member

bk138 commented Nov 20, 2019

@KWBerry dupe of #346 ?

@KWBerry
Copy link
Author

KWBerry commented Nov 20, 2019

Yes I believe it is a duplicate of #346.
I did not know it was already reported, and I'm new at this and didn't know how to check.

My apologies !

Kenneth Berry

@KWBerry KWBerry closed this as completed Nov 20, 2019
@bk138
Copy link
Member

bk138 commented Nov 20, 2019

No prob! d87d255 and d1a134c should have fixed it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants