It turns out that all of the "good" stuff has been done on policy-based setting of the WinVNC server configuration. At this point, there is nothing I can value-add to the material already collected by Daniel QUinlan (and even Andrew Stockton has done some policy stuff).
One thing I think might help would be to provide a tool to automatically retieve the registry settings for a WinVNC server, then layer them to show what the effective settings actually are, so I'm starting to work on that. Unfortunately my C++ skills are still in infancy; since I have most of the code for this in VB already, I am starting this in VB5. The initial step I have planned is just the class module to do registry key enumeration. Comments and code welcome; as soon as I have some basics available, I will post the source code and a DLL. Other notes- (1) I am using VB5 as a compiler since that is the earliest available version which gives me the functionality I need. This means there will be a dependency on msvbm50.dll - but that is present on the vast majority of Windows systems I encounter these days. (2) The code I produce will be an ActiveX DLL to expose it as much as possible to easy use by admins. Any front end will be a small separate executable that just references the DLL. (3) I am working from "free" sources to develop the whole module; the module itself will be standard GPL-licensed code. --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
