Multithreaded AES DSM Plugin

[adzm]

New builds are now available for Windows 2000 support.

[redge]

There is not a complaint but a minor problem logic naming convention and release file version.

version release NOK
priority change.
SecureVNCPlugin.dsm 1.0.1.0 = ARC4...AESv3 client and server
SecureVNCPlugin.dsm 1.0.2.0 = AESv3...ARC4 client and server


naming OK
version release NOK
SecureVNCPluginAES.dsm 1.0.1.0 = AESv3 server only
SecureVNCPluginARC4.dsm 1.0.2.0 = ARC4 server only

downloaded 17 October 2009, verified on XP Pro SP3
Vista/7 tab detail can't check version, nothing
right click on SecureVNCPluginARC4.dsm and new SecureVNCPlugin.dsm
(all 4 files are version = 1.0.0.0 !!!!)

[redge]

bug SecureVNCPlugin.dsm (config button, viewer connected)
no private key, no public key

viewer connected to server
at server, press config
not modify but just look SecureVNC information version.
server: WLAN 54 Mbit/s
viewers: LAN 100Mbit/s

vncviewer 1.0.7.8 (17 October 2009)
winvnc 1.0.7.7 (13 october 2009)


vista, single vncviewer securevnc 1.0.2.0 connected to single server securevnc 1.0.2.0 win7rc, NOK
= restart winvnc

vista, single vncviewer securevnc 1.0.2.0 connected to single server securevnc 1.0.2.0 xp pro sp3, NOK
= crash winvnc

vista, single vncviewer securevnc 1.0.2.0 connected to single server securevnc 1.0.1.0 xp pro sp3, NOK
= crash winvnc

vista, single vncviewer securevnc 1.0.2.0 connected to single server securevnc 1.0.1.0 win7rc, OK


win7rc, winvnc securevnc 1.0.1.0 reverse connected to single vncviewer listening securevnc 1.0.2.0 win7rc, OK


win7rc, winvnc securevnc 1.0.1.0 reverse connected to repeater,
single vncviewer listening securevnc 1.0.2.0 win7rc initiate connect to repeater ID:12345678, match ID:12345678 OK


3 vncviewers(xp, win7rcB,win7rcA) securevnc (1.0.10 and 1.0.2.0) to single vista winvnc securevnc 1.0.2.0, OK



suggestion vncviewer + encryption plugin version connected title
catching easy know wish encryption in use:
Ultra@VNC Viewer 1.0.7.8 + SecureVNC Plugin 1.0.10 AESv3 - vAdam D.Walling
Ultr@VNC Viewer 1.0.7.8 + SecureVNC Plugin 1.0.2.0 ARC4 - vAdam D.Walling


otherwise, that working very well, so great work

[Cobra]

Hi everyone,

I just installed UltraVNC v1.0.8.0 on a Windows 7 machine. I encountered the same problems as I reported before under Windows Vista (see posts above). There's no possibility to save the changes in the configuration via the icon in the taskbar -> Admin Properties. I had to use the menu entry Edit Settings and the restarting the machine to take effect...

Can you confirm those problems as well? Is there another workaround how you can save those settings without restarting the machine?

Thanks for your help!

Cobra

P.S. The AES-Plugin works perfectly! The only thing I realized was, that it takes some time connecting to the server. I guess it has to do with the handshake and sharing the keys.

[Rudi De Vos]

You only need to restart winvnc before the changes take effect.
Running as service (close winvnc), the service auto restart it.

[Cobra]

Hi Rudi,

Wow... What a fast reply - better than any paid service support agreement! I'm aware of this workaround. But is there a possibility to save those settings via Admin Properties?

Thanks for your excellent support!

Cobra

[Rudi De Vos]

What a fast reply... lol, I'm having a holliday, normal it isn't that fast.


It works on my win7 system

Normal, you should see a popup that tell that ultravnc try the make changes to your system -> click detail and you see that he want to write
a ultravnc.ini in the system temp folder.

The system restart winvnc as console user and then execute the saving
with a "runas".
-uac need to be enabled
-runas need to work
-the current console user need to be detected, there are some reports that when the console user is a non local user, winvnc have trouble finding the credentials and unable to start an extra instance of winvnc as that user.

It sounds complex, but the problem is that a service has access to all files.
To prevent a normal user to be able to make changes the service first need to start winvnc as console user, tkae his credentails and then try to make the changes....