Phil,

Just looking at those now. Kenny Kerr has some sample code that is interesting 
- but am not sure if I can actually use it.

Dino

-----Original Message-----
From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf 
Of Wilson, Phil
Sent: Friday, 12 October 2007 04:37
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Storing passwords securely - or can I do 
something else?

Just a thought: Would the Credential APIs work for you? CredRead, CredProtect, 
CredWrite etc? 

Phil Wilson 

-----Original Message-----
From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf 
Of Dean Cleaver
Sent: Monday, October 08, 2007 9:49 PM
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

Reply via email to