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
VNCVIEWER.EXE and MS authentication
VNCVIEWER.EXE and MS authentication
Is there a way to pass the domain\username and password to the VNC viewer on a command line or .vnc file?
LS login
I agree. I wouldn't do it myself but there have been numerous VNCScan users that have requested that their password be saved in VNCScan.
I could encrypt their login information so that it's not easily hacked so the security problem that you're talking about wouldn't be an issue.
Here's what I'd like to do:
The user puts his/her password into VNCScan.
VNCScan encrypts the user/pass into the XML file with a key tied to that computer. If someone grabs their XML file, it will be pretty much useless on another computer.
If they double-click on a computer, I'd like VNCScan to write the .vnc file, launch the viewer against it, then immediately delete the .vnc file. This would prevent the password from just hanging around on the computer.
I think that these measures would make this feature safe enough for anyone not working for the DOD.
I could encrypt their login information so that it's not easily hacked so the security problem that you're talking about wouldn't be an issue.
Here's what I'd like to do:
The user puts his/her password into VNCScan.
VNCScan encrypts the user/pass into the XML file with a key tied to that computer. If someone grabs their XML file, it will be pretty much useless on another computer.
If they double-click on a computer, I'd like VNCScan to write the .vnc file, launch the viewer against it, then immediately delete the .vnc file. This would prevent the password from just hanging around on the computer.
I think that these measures would make this feature safe enough for anyone not working for the DOD.
I could see how it could be useful to have for at least the command line options (at least username). . .even RDP and ICA clients allow this. . .though I don't like the idea of a password being in clear text at any time. . .I think it is Citrix that allows you to pass an encrypted password to the command line. . .

