How about storing the key on a remote server ? When you need it you connect to it get it. Or extending on this idea; you could store the key on a remote server, when you need to authenticate you call the authentication code on the remote server side and have it spit back a bool (true = user is authenticated / false = user need to try again). I haven't actually implemented this but in theory it should work.
-Pete -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Farhan Sh Sent: Monday, May 13, 2002 8:58 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Hide part of code from Developers I know that's the problem. I can put the key in registry and read it on runtime but that's not safe either. Any other ideas? You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
