This is just *way* too easy. The big problem here is that the registry is a terribly insecure place to store this information. I can see now why the documentation essentially says that the registry usage system is a crude "short-term" hack.
----- Original Message ----- From: "Niko Papula" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, 2002-04-20 02:30 Subject: RE: vncpasswd for Windows > Hello > > Jacob Hoover wrote: > >What OS's are you running on? I may be able to help you. I took the > > vnc password source and put it into a separate app with registry > > access. It allows you to read and write passwords on the local and > > remote machines. However, I have only tested it on NT 4.0 -> NT 4.0 > > scenario's. > > I have done similar thing. Reading and writing VNC password to Windows > registry is no problem if you know the encryption scheme and encryption > key. Easiest way would be to use the corresponding file from VNC source. > > I have implementation that works on at least W95, W98, WNT, W2000 so I > expect Jacob4s implemention to work on these same OSes as well. > > Regards > > > Niko Papula > > P.S. The easy decryption of VNC password in registry is a security risk. > --------------------------------------------------------------------- > 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 > --------------------------------------------------------------------- --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
