I think it would be very nice if in the client the checkbox is by default activated if the plugin is in the same directory as the client...
Greets and big THX,
Andy
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Auto Activate Crypto-Plugin
-
An Interested User
Auto Crypto
I don't agree. I manage multiple machines, some that need encrypted connections (they are connected directly to the Internet), and some that do not (I access them behind a firewall, either directly on the LAN or through a VPN connection). The majority of new connections for me are behind that firewall, and it would be irritating to turn that off every time (though I would get over it if it were done).
What I would like to see instead is the ability to specify whether to use the encryption plug-in on a connection-by-connection basis (speaking of the .vnc files -- this part is already in Ultr@VNC), as well as the ability to specify what encryption key file to use on that same basis (so that multiple keys can be used and managed).
This latter ability is not currently in Ultr@VNC, but it could be done if the plug-in architecture would allow parameter passing (I already talked with the author of the encryption plug-in, who is very supportive of this idea).
What I would like to see instead is the ability to specify whether to use the encryption plug-in on a connection-by-connection basis (speaking of the .vnc files -- this part is already in Ultr@VNC), as well as the ability to specify what encryption key file to use on that same basis (so that multiple keys can be used and managed).
This latter ability is not currently in Ultr@VNC, but it could be done if the plug-in architecture would allow parameter passing (I already talked with the author of the encryption plug-in, who is very supportive of this idea).