On Win7x64 I installed UltraVNC-x64-1.1.8.0 and put SecureVNCplugin-x64-2.3 to the folder of the program. And it does not work properly. Yes, it allows to generate server and client keys, and it seems, encryption works. But I want to make UltraVNC to not ask any passwords at all, and I do not know how. In the SecureVNCplugin configuration menu all items are gray (disabled), and it is impossible to choose any "Enabled ciphers", any "Enabled key lengths", "RSA", "Passphrase" etc. Only buttons for key generation, website, and closing are active. What should I do to make other options available? Thank you!

winvnc.exe ( 64bit version) This normal install in C:\Program Files\ and use the SecureVNCPlugin64.dsm winvnc.exe (32bit version) This normal install in C:\Program Files (x86)\ and use the SecureVNCPlugin.dsm What does the about tell, 32 or 64bit.

It doesn't matter where you copy it, you need to use the correct plugin.If you want to use it as service it need to be in a secure folder ( program files..)

Just a quick question: I noticed by accident that the SecureVNC plugin on an Win 8 uvnc installation identifies itself as version 2.4.0.0. while an installation on a win 7 machine identifies as V.2.3.0.0. (both with uvnc 1.1.8..

Is that correct and why can't I install v.2.4.0.0 on win 7? Any win 8 specific changes or something like that?

I also have a question - why does SecureVNCPlugin.dsm from uVNC's "addons setup package" 412,920 bytes while the official version (the one which has its own site) is 404,992 bytes?Both of them state they're v2.3.

The SecureVNC plugin is crashing on Windows XP, because it depends of FlsAlloc API set from Kernel32.dll that is not supported on Windows XP, only in Windows Server 2003.There is a chance to this dependecies get removed in a new version? I ask this because in the plugin web page, it says that plugin supports the Windows XP.

The passphrase for the Plugin seems to be restricted to certain characters. A randomly free password generation (for example by password maker) is not usable. Certain special chars however work. Maybe there could be a hint included into the documentation about the permitted charset.

The exact charset permitted respectively not permitted is still unknown to me.The error message in the case of characters out of range of the permitted charset is misleading:

server closed connection - The server running as application

I spent two debugging session on the matter, what in the world the thing could be, which makes the server think it being run in application mode (what is simply nonsense). In the end it was the passphrase being correct but nonetheless obviously unreconizable.

To my surprise, when i do enter the passphrase in a DIFFERENT window, the copy and paste it into the login window of the viewer, the exact same passphrase that seconds before lead to the message...

server closed connection - The server running as application

...does correctly establish the connection.As soon as i try to enter the passphrase in the login dialog directly, the message is again that written above.

Thus, it seems that the login dialog prevents the input of some special characters.