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

config files (*.vnc) associations

Post Reply
plastikat
Posts: 5
Joined: 2008-11-19 15:00
Location: Russian Federation

config files (*.vnc) associations

Post by plastikat »

Hello 2 all,

After upgrading 1.0.5.4 to 1.0.6.4 i've subsequently found out that new vncviewer traces config files (*.vnc) associations registry entry, located here:

Code: Select all

[HKEY_CLASSES_ROOT\VncViewer.Config\shell\open\command]
(default)="C:\Program Files\UltraVNC\vncviewer.exe" -config "%1"
Given above is the default value, and if i change it somehow then after clicking any *.vnc file it is restored back to default...
Actually i have been using it a little bit strange but useful way (you may look here for details [topic=12174][/topic]) and now it became impossible with new vncviewer... It is probably some kind of a security issue, but some other people could use this way to supply some other common-to-all options. Was that 'guarding' done intentionally?
Post Reply