Groups | Blog | Home
all groups > dotnet security > march 2006 >

dotnet security : Encrypting connection strings across dev environment


Becky VanBruggen
3/31/2006 6:35:02 AM
I'm in the process of trying to create a template ASP.NET 2.0 web site for
all the developers in my group. I'd like to encrypt the connection strings
for commonly used databases and put them in every developer's machine.config
file. However, I'm not sure the best encryption to use.

1.) Do I use a machine-level container?
2.) Do I use a user-level container?
3.) Do I use no encryption in the dev environment and just implement that in
the production environment?
4.) Do I treat my developers like a web farm and deploy a single key to
everyone?

Becky VanBruggen
3/31/2006 7:40:03 AM
About 6-8 developers.

Thanks for your help.

[quoted text, click to view]
Mitch Gallant
3/31/2006 10:24:10 AM
How many devs? Is small number consider having separate encryption
credentials for each dev (e.g. an RSA keypair for each).
- Mitch

[quoted text, click to view]

Dominick Baier [DevelopMentor]
3/31/2006 3:33:36 PM
i wouldn't go through the hassle of encrypting the config strings on the
dev machines -

devs are smart enough to call ConfigurationSection.Unprotect() :))

why do you want to protect the connection string? are there usernames and
password embedded? better go for windows integrated autentication - if there
are no secrets - then there is nothing to hide.

i would implement encryption of config files as part of your deployment process
to a production server

besides that - always use the machine container for ASP.NET

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

[quoted text, click to view]

AddThis Social Bookmark Button