This post originated from an RSS feed registered with Web Buzz by Josh Baltzell. Original Post: How are we supposed to hide important information in our .NET apps? Feed Title: ShortDomainName.com Feed URL: http://www.contegix.com/Rss.aspx Feed Description: Weblog of Josh Baltzell. Focusing on the computer industry and .NET programming related news. I like to get involved on the discussions wherever they are. Latest Web Buzz Posts Latest Web Buzz Posts by Josh Baltzell Latest Posts From ShortDomainName.com

I talked to Josh Pollard about this earlier and he posted a full question about it on his site.  He is more or less asking how the hell we are supposed to hide necessary logins and passwords in our .NET apps?

We looked at the MSDN article about storing this stuff in the registry encrypted with ACL or LMNOP or yippity-yap or whatever they say, but Josh pointed out that that sort of defeats the coolness of XCopy deployment.

So what is the right way to do this stuff?  Not just plain SQL connection strings, but other login password info that you might need on the site.

Why isn't this simple?  When it comes down to it most data driven apps would need this.

[READ]