I am using vnc2swf http://www.unixuser.org/~euske/vnc2swf/ to record remote vnc sessions. If you are not familiar with the software it generates a vnc connection to the localhost and starts to record the session to a flash movie.
When its run it has an interface to enter the vnc password and the port the host is configured on. However I'm using the command line options to make it more automated.
vnc2swf.py -n -o c:\NameOfFlash.swf -t video -P PasswordFile 127.0.0.1 5900
The issue is with the password file. In the documentation for vnc2swf it refers to this file as the Linux password file. I'm using windows and found a tool called vncpasswd.exe which comes with vncSnapshot and this seems to correctly make a "password file". When I look in the file the data is encrypted, but it does not work.
Tried using the hex version of the password as my password file (does not connect)
Tried using an encrypted version of my plain text password (does not connect)
Tried using plain text password for my password file (this works)
The only way I can get it to work is if my password is in plain text.
So my question is:
Does windows VNC allow to automatically script the password to connect? I know that I can create a session file and have the password saved in this file. But can that same thing be done with just calling a file wtih nothing in that file but the password.
Thanks for the help
[mod=3406,1161984126] Moved topic per users request [/mod]
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
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- 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
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- 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
vnc2swf and the password file
vnc2swf and the password file
Last edited by Silvos on 2006-10-27 21:22, edited 2 times in total.
Re: vnc2swf and the password file
The developer of vnc2swf has let me know that the password file currently only supports plain plain text, and that encryption should be in the next version.
I have a workaround until then.
I use vncpasswd.exe to create a password file, using random characters as a password. Something like %^(w!&#z. The vncpasswd.exe creates an encrypted password file based off %^(w!&#z. The new encrypted output is what I use for the password file, and is the password I use for VNC remote connections.
The above does two things
1. If the password file is found the data inside is garbled, and its not apparent that its a working password.
2. if a user tries to remotely discover the password via registry, the code that is found will not work to log into vnc. The only pass that will work is the one in the password file.
For the clients that are allowed to connect, they are given a vnc connection session file. This automatically connects them so they don't have to enter or remember a complex password.
Hope this helps someone!
I have a workaround until then.
I use vncpasswd.exe to create a password file, using random characters as a password. Something like %^(w!&#z. The vncpasswd.exe creates an encrypted password file based off %^(w!&#z. The new encrypted output is what I use for the password file, and is the password I use for VNC remote connections.
The above does two things
1. If the password file is found the data inside is garbled, and its not apparent that its a working password.
2. if a user tries to remotely discover the password via registry, the code that is found will not work to log into vnc. The only pass that will work is the one in the password file.
For the clients that are allowed to connect, they are given a vnc connection session file. This automatically connects them so they don't have to enter or remember a complex password.
Hope this helps someone!