That is something I considered - this whole thing is so that admins can run their jobs as different user accounts if they want to - but given they will be compiling some of the code themselves, if they want to impersonate a user, they could code that themselves and then obfuscate it.
Dino -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Roberts Sent: Wednesday, 10 October 2007 01:14 To: [email protected] Subject: Re: [ADVANCED-DOTNET] Storing passwords securely - or can I do something else? You could try Obfuscating your code. The Dotfuscator will encrypt any or all of your string objects and give you some security! -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Dean Cleaver Sent: Tuesday, October 09, 2007 12:49 AM To: [email protected] Subject: [ADVANCED-DOTNET] Storing passwords securely - or can I do something else? As part of an automation system I've written, I'd like to be able to specify the account that certain jobs are executed under - but to do so, I presume I would need to store the username and password in the database - something I'm not overly keen on even if the passwords are encrypted. Given the flexible nature of the system, there's not a lot of other choices left to me. Or is there some other token I can store that I can use? Dino =================================== This list is hosted by DevelopMentor http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
