> It hasn't been addressed in either the original or tridia releases as far
as
> I am aware.
>
> I have a little addennum that I have tested on my Win2K box that resets
the
> permissions upon server/service start, I should really get around to
> contributing that code for WinVNC. I no longer have NT 4.0 around to test
> with, so I am willing to give the code/binaries to anyone running NT 4.0
to
> see if it fixes this problem. I'm working with the tridia source code
base,
> but it's easily backportable to the original 3.3.3r7 source base.
If you have any example code that sets the appropriate permission then I'll
happily take a look with a view to including it.
> However, the install files (which are not anywhere I can find) are the
best
> place to correctly set registry permissions in the first instance. Does
> anyone have access to these? I have InstallShield for VisualC++ 6, so I
can
> recompile the installer once I have a look at the install source, assuming
> that winvnc uses InstallShield (it certainly smells like an IS install to
> me).
If you "correct" the registry permissions during install then WinVNC won't
operate correctly as an application, since it won't have permission to read
the password part of the local machine registry. Setting the permissions
during -install is probably the best compromise, although it's not clear
whether the registry should be reverted during -remove.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
