I have a few ideas, but would like to get another opinion (or recommendation)
on bast practices for encrypting sections of configuration files. I have an
application (ClickOnce deployed) that utilizes a shared configuration file on
a network share (Microsoft Enterprise Library). This shared configuration
file stores connection string data (among other information). What would be
the best way to encrypt the connection string information in the shared
configuration file, and have everyone be able to decrypt it?

If you are already using Enterprise Library for your conf files, why not use
its built in capabilities for encrypting? The practices they use are good
and usually pretty easy to deploy as well.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"MichaelN" <MichaelN (AT) nospam (DOT) nospam> wrote