lwc wrote:I'm sorry, I forgot to mention the viewer would use the plugin to access multiple SingleClicks. What does it take to enable the options and how many bits of defense do I get by default?
The plugin's docs don't mention that advanced option, which is why I ask in here.
Yeah, I tripped over it someplace deep when I was reading up on this. Same answer: you don't want to change that unless you have a special need.
The Plugin is controlled on the server side, and I think the default is AES 256-bit encryption. You will see what it is set to when you open the Plugin control panel on the server. I changed all of mine to ARC4 56-bits. I'm only really interested in having more secure passwords on my connection than worrying somebody will want to spy on my remote sessions. I find the reduced settings faster to connect and reduces the network load.
If your going to use the VNC Viewer GUI for your connections, you can CHECK or UNCHECK the "Use DSMPlugin" for each session. I find it MUCH more useful to make SHORTCUTs with different command-line options for each machine I want to remote control. Then you can pre-specify all the options you want.
For example, a non-secure connection would have a shortcut properties of:
- Code: Select all
"pre-existing PATH to VNCviewer.exe" /password 8chars!! -loglevel 12 -console 10.0.0.69
The "-loglevel 12 and -console" are for debugging purposes, and can me removed when its all working.
The same thing, but encrypted with a much better password - handled by the plugin.
- Code: Select all
"pre-existing PATH to VNCviewer.exe" /password LetMeIn2012! -loglevel 12 -console -dsmplugin SecureVNCPlugin.dsm 10.0.0.69
I use both of these in Windows XP Pro SP3. Up to this Windows version, command line parameters go OUTSIDE of the quotation marks around the programs' path string. This may not always be the case, I leave it to the reader to adapt to your Windows version.
Also, if your using a 64-bit O/S then the Plugin name is different. I leave it to the reader to adapt as needed.