SecureVNCPlugin64.dsm

[YY]

I have been trying to get this plugin to run on my UltraVNC SC connection without any luck.

- Generated pubkey and pkey. both keys stored in ultravnc program files

I had make a successful UltraVNC SC connection with SecureVNCPlugin (not SecureVNCPlugin64)

I don't have a 64bit system to test, but I believe only the 32bit SecureVNCPlugin is working under UltraVNC SC, as the winvnc.exe of UltraVNC SC is most likely a pure 32bit program.


At viewer end, you need to have the pkey only, my setting is:
-dsmplugin SecureVNCPlugin.dsm -listen 5500

I have not put anything in my custom.zip should there be a pkey file in my custom.exe?

This is the problem, the pubkey is required at the sc.exe package. But if you want to creat the sc.exe by using the online creator, there are some tricks:

1. The SecureVNCPlugin.dsm must be put into custom.zip. But UltraVNC SC knows the name msrc4plugin.dsm only, so you must rename it as msrc4plugin.dsm
2. The pubkey must be put into the custom.zip. But the online creator will remove all key file other than the one named rc4.key, so you must rename it as rc4.key
3. Then you can upload the customer.zip, but you should use the RC23 or Rel.1 creator only. Don't use the 2009 creator, as it always provide its own msrc4plugin.dsm (ver 1.2.4.0)
4. Finally, when you download the UltraVNC SC (custom.exe), you must rename the pubkey file (you had named it as rc4.key) to its original name (it should be something like xxxxx_Server_ClientAuth.pubkey). You may use 7-zip to open the sc.exe and making the change.


That it!

[cliffyb1]

Thank You so much Redge and YY your tips/tricks worked perfectly I never would have figured that out without your help

[racassel]

This is nice, but with unsigned DLL, the program generate a red WARNING THIS PROGRAM MAY HARM YOUR COMPUTER is not professional when helping clients.
Its a lot of work, to find out this flaw. When will the compiler be fixed to generate sc.exe with updated to work with SecureVNCplugin.dsm ?

[racassel]

Can you then also replace winvnc.exe and vnchooks.dll with the latest 1.0.9.6.2 version to take advantage of all the improvements since 2005 version?