aspnet_setreg in Server 2008
The aspnet_setreg utility is very useful for storing encrypted domain credentials, connection strings and other values referenced in a web.config which should not be visible in plaintext.
One such technique is when using the .Net “impersonation” mechanism. Typically, this would look something like:
<system.web> <identity impersonate="true" userName="WindowsDomain\YourUserName" password="YourPassword" /> </system.web>
However, if you download and unzip/install the aspnet_setreg utility, you can now use the following syntax to store these credentials in a binary encrypted field in the registry:
c:\Tools>aspnet_setreg.exe -k:SOFTWARE\MY_SECURE_APP\identity -u:"yourdomainname\username" -p:"password"
Your web.config should now be updated to reflect the new stored values. (Note: this is the exact syntax, don’t replace username and password with your own…):
<identity impersonate="true" userName="registry:HKLM\SOFTWARE\MY_SECURE_APP\identity\ASPNET_SETREG,username" password="registry:HKLM\SOFTWARE\MY_SECURE_APP\identity\ASPNET_SETREG,password" />
An important thing to note is in Server 2008 on a 64 bit machine after running this utility is a different location it is stored in the registry. To find it you must browse to:
[HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node]
You can then right click and export this key from here, then open the .reg file in notepad and change to the correct key and import. The end result should be a reg file to import that looks like this:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\Software\MY_SECURE_APP] [HKEY_LOCAL_MACHINE\Software\MY_SECURE_APP\identity] [HKEY_LOCAL_MACHINE\Software\MY_SECURE_APP\identity\ASPNET_SETREG] "userName"=hex:01,00,00, etc "password"=hex:01,00,00, etc
References
MSDN, http://support.microsoft.com/kb/329290
ASPDEV, http://www.aspdev.org/articles/web.config/
ASPNET FORUMS, http://forums.asp.net/t/1650965.aspx/1?aspnet_setreg+under+Win+2008
Posted on March 8, 2011, in Programming & Development, Security & Cryptography and tagged .net 4, .net 4.0, aspnet_setreg, domain, registry, server 2008. Bookmark the permalink. 3 Comments.
Thanks for your help
Pingback: Logon failure: unknown username or bad « Fraction of the Blogosphere
Pingback: Logon failure: unknown username or bad password « Fraction of the Blogosphere