After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome

2025-12-14: 1.7.1.X-dev release builds need tests and feedback: https://forum.uvnc.com/viewtopic.php?t=38134

2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page

2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078

2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome

Maintenance

Should you have problems with the MS-Logon plugin? Here is the place to look for help or report issues
Post Reply
b2pi
Posts: 5
Joined: 2004-11-09 21:45

Maintenance

Post by b2pi »

Is any one maintaining this? I rather suspect, considering the vulnerabilities, that it might be nice to do this with a gina stub
B
800
800
Posts: 2337
Joined: 2009-09-09 14:05

Re: Maintenance

Post by B »

Huh? I thought this was an integral part of the distribution and was being maintained as a matter of course?
b2pi
Posts: 5
Joined: 2004-11-09 21:45

Re: Maintenance

Post by b2pi »

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...
B
800
800
Posts: 2337
Joined: 2009-09-09 14:05

Re: Maintenance

Post by B »

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.
Post Reply