--- Peter Vertes <[EMAIL PROTECTED]> wrote: > 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
You could simply look for the code that gets it from the remote server and see what the return value is. > 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. Again someone could do the same. There is no real solution to hiding secrets in code. Only things that will make it harder to find. Peter Foreman __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
