Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Bug report

Post Reply
AlexJ
Posts: 1
Joined: 2010-02-13 22:17
Location: Michigan, US

Bug report

Post by AlexJ »

UltraVNC v.1.0.8.2:

Test boxes: Windows XP Pro SP3.

If checkbox "Run and configure after install" is marked in the setup, then on stage of creating rc4.key the key is placed in the system directory
c:/windows/system32
WinVNC.exe works fine and can find rc4.key, but when vncviewer running in listening mode it can not find the key and does not allow remote connection since password authentication always fail. After removing rc4.key to the "home" of uVNC everything work as expected, both winvnc and vncviewer recognize a key then.

BTW, just suggestion:
May it would be better to place all writable files (ultravnc.ini, rc4.key...) to the %Application Data% as it advised by M$ for WinXP and is requirement for Vista and 7 ? (Virtualization still work on Vista & 7, but M$ says it could be stopped anytime)
In corporate networks c:\Program Files, c:\windows always locked down to read only, but %Application Data% is official legal writable directory for applications as it advised by OS maker. Of course Admins could adjust ACLs for UltraVNC, but... I believe Microsoft is right on that decision to disable write access to system directories.

Best regards and thanks to the UltraVNC team

Alex.
Last edited by AlexJ on 2010-02-13 23:11, edited 1 time in total.
Post Reply