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
2026-04-01: After 1.7.x, 1.8.x release builds need tests and feedback: https://forum.uvnc.com/viewtopic.php?t=38158
2026-03-11: CVE-2026-3787 and CVE-2026-4962 - Clarification: https://forum.uvnc.com/viewtopic.php?t=38155
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
Help is very needed for:
Windows ARM/ARM64 support: https://forum.uvnc.com/viewtopic.php?t=38163 / https://github.com/ultravnc/UltraVNC/issues/346
macOS support: https://forum.uvnc.com/viewtopic.php?t=38164 / https://github.com/ultravnc/UltraVNC/issues/347
Linux support: https://forum.uvnc.com/viewtopic.php?t=38165 / https://github.com/ultravnc/UltraVNC/issues/348
*BSD support: https://forum.uvnc.com/viewtopic.php?t=38166 / https://github.com/ultravnc/UltraVNC/issues/349
*Solaris support: https://forum.uvnc.com/viewtopic.php?t=38167 / https://github.com/ultravnc/UltraVNC/issues/350
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
2026-04-01: After 1.7.x, 1.8.x release builds need tests and feedback: https://forum.uvnc.com/viewtopic.php?t=38158
2026-03-11: CVE-2026-3787 and CVE-2026-4962 - Clarification: https://forum.uvnc.com/viewtopic.php?t=38155
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
Help is very needed for:
Windows ARM/ARM64 support: https://forum.uvnc.com/viewtopic.php?t=38163 / https://github.com/ultravnc/UltraVNC/issues/346
macOS support: https://forum.uvnc.com/viewtopic.php?t=38164 / https://github.com/ultravnc/UltraVNC/issues/347
Linux support: https://forum.uvnc.com/viewtopic.php?t=38165 / https://github.com/ultravnc/UltraVNC/issues/348
*BSD support: https://forum.uvnc.com/viewtopic.php?t=38166 / https://github.com/ultravnc/UltraVNC/issues/349
*Solaris support: https://forum.uvnc.com/viewtopic.php?t=38167 / https://github.com/ultravnc/UltraVNC/issues/350
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.
