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
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
Maintenance
Maintenance
Is any one maintaining this? I rather suspect, considering the vulnerabilities, that it might be nice to do this with a gina stub
Re: Maintenance
Huh? I thought this was an integral part of the distribution and was being maintained as a matter of course?
Re: Maintenance
Perhaps maintaining is the wrong word. MSLogon 2 uses NTLM, which Microsoft has advised not to use. It would be best to use Kerberos if available to connect to an AD domain. Also, I had thought that the original implementer (Mascha?) had left for other pastures...
Re: Maintenance
Wow, you seem to go way back!
Yeah, now that you mention it, it always did seem a little "quaint" the way MSLogon prefers using local groups first (though that does make it fit well with home LAN users). Honestly I didn't know it lacked Kerberos support; I'm surprised. But MSLogon's not a feature I use ordinarily.
In short then, yes, I would agree an update would be valuable.
Yeah, now that you mention it, it always did seem a little "quaint" the way MSLogon prefers using local groups first (though that does make it fit well with home LAN users). Honestly I didn't know it lacked Kerberos support; I'm surprised. But MSLogon's not a feature I use ordinarily.
In short then, yes, I would agree an update would be valuable.