Re: SecureVNC DSM Plugin

bigdessert · Post by **bigdessert** » 2010-03-27 06:01

Two questions:
- Does this plugin support working over the UltraVNC Repeater?
- You have separated 32/64-bit plugins... What if we support clients using a UltraVNC SC (Single Click) and they have both 32-bit and 64-bit systems? Do we need to have two different .exe builds?

Thanks

adzm · Post by **adzm** » 2010-03-27 23:40

Yeah, it works fine over the Repeater. Also the 32-bit version of UltraVNC and the Plugin will work out on x64 systems just fine; that is how we do it.

B · Post by B » 2010-03-29 13:26

Fine work, Adam. VNC desperately needs this.

Shared keys are for suckers.

Have you looked into the problems encountered by supercoe (ChunkVNC dev) and others?
I don't have a link handy, but they've experienced instability that has kept them from endorsing the plugin.

adzm · Post by **adzm** » 2010-04-02 13:37

I'll have to look into it. A lot of issues seem to come from limitations in the original DSM architecture. I am working on a new version that has more integration with VNC rather than simply modifying the data stream to include the handshake. H

redge · Post by **redge** » 2010-04-02 23:36

adzm

welcome back

brief case
vncviewer -dsmplugin securevncplugin.dsm -listen

winvnc without plugin connect to vncviewer with plugin
status secure connection... wrong.

applicable only to securevncplugin 1.0.2.0
cmd run as administrator>winvnc -kill = crash winvnc with vncviewer connected

YY · Post by YY » 2010-04-03 03:35

redge wrote:brief case
vncviewer -dsmplugin securevncplugin.dsm -listen

winvnc without plugin connect to vncviewer with plugin
status secure connection... wrong.

Hi! redge,

Which status you are talking about?

If you mean the Status Windows of vncviewer when getting connected, I found the same problem when using MSRC4Plugin.

Looks like this is the problem of vncviewer rather than the particular plugin.

redge · Post by **redge** » 2010-04-03 05:39

YY wrote:Which status you are talking about?

vncviewer status,
you are right, i was using example of securevnc.dsm but this also applicable to msrc4plugin.dsm in this case.

adzm · Post by **adzm** » 2010-04-05 01:14

For the most part, a lot of problems come from the plugin architecture itself. It has been used for far more than it's original intention. However I will definitely take a look and try to patch up these issues regardless of where the bug exists.

supercoe · Post by **supercoe** » 2010-04-05 22:59

The link to the SecureVNC issue is stickied:
- https://forum.uvnc.com/viewtopic.php?t=16789

adzm,

Redge has mentioned that the possibility that you could fix the problems with SecureVNC, I just want to let you know that your effort would be appreciated greatly!

adzm · Post by **adzm** » 2010-05-13 01:28

That status only shows the currently loaded DSM plugin, but does not actually reflect the current encryption status.

My new changes to the plugin architecture provide a better way of handling this. You'll be able to see exactly what encryption parameters are being used.

I am doing my best to get this ready for the community as soon as possible.