UltraVNC 1.1.9.0 + SecureVNC 2.3.0.0 Broken Again?

[UltraHead]

Hi there,

it looks like the current version 1.1.9.0 can't be used together with the SecureVNC 2.3.0.0 plugin, again? (like it was with version 1.0.9.6)

I installed a fresh, clean version of the server (WinXP SP3, x86) and the client (also WinXP SP3, x86), added the SecureVNCPlugin of the current addons to both of them, created a key pair with the client and copied the public key to the server to authenticate my client. And then I got the exact same behaviour as described within this topic I found with google: https://forum.ultravnc.net/viewtopic.php?f=54&t=27830.

I had to "resolve" this problem by downloading the binary archive of version 1.0.9.6.2, replacing all files with their old version. Unlike two years ago it wasn't enough to replace only the vncviewer.exe on the client side because the server complained about the client being too old.

It would be nice to get this fixed up again because the older version seems to have some more bugs left (e.g. the client steals my copy-hotkeys with enabled automatic synchronization of the clipboard, even when the windows is in the background, which is quite annoying).

Best regards.

[Rudi De Vos]

Still need to check it, just a bump to put the post back on top

[Rudi De Vos]

I can not repeat it using latest server and viewer (1190)

tested

viewer connect to server with encryption key set
*vnc passwd set
*blank passwd

server connect to viewer with encryption key set
*vnc passwd set
*blank passwd

How did you tested it ?

[UltraHead]

Sorry for the inconvenience,

suddenly I'm unable to reproduce the problem myself?!
As I mentioned last week, I switched back to version 1.0.9.6.2. To test anew I had to copy the new file back into the viewer and re-set up the test server (which I dumped meanwhile). After copying the public key of the client to the server, I was able to connect to the server using my configured VNC-password. The title bar of the viewer and the status window are showing the use of the SecureVNCPlugin.

So please accept my apologies and thanks for your great work!

[Rudi De Vos]

Runing as service it's not always clear what exe is running... possible some versions were mixed.

[UltraHead]

Yes, I've noticed that there are two winvnc.exe-processes running when I start the additional service.

Now I also do stop the service (and with this all running winvnc.exe-processes halt) when I changed something in the configuration, just to be sure the new configuration is really applied to all (have to be restarted) processes. I saw process-IDs switching multiple times in the task-manager while starting the server through the start-menu and then starting the service through the server's context menu. So I assume there are multiple processes started and terminated (also switching from my local user to the SYSTEM-account) while performing such administrative tasks.
(Last week I changed the configuration of the SecureVNCPlugin multiple times since I didn't know that it does not need any special configuration, all without restarting the service. Maybe it's possible that some of these processes used different, faulty configurations.)

[Rudi De Vos]

2 processes is normal
The same winvnc.exe is used as service and engine.

1x service running in session 0. Session 0 is isolated and can not interact with the desktop.

1x running in the console session. This instance can interact with the desktop of the console session.
This instance is started by the service and restarted when session/desktop change.

see session id in the taskmgr