Thinking about this, if someone who is hostile (read, would use the
connection string maliciously) has rights to the directory the web.config is
in and can actually open up that file in a text editor, you have bigger
security problems at hand to worry about than whether or not they can get a
connection string. This would immediately indicate your security is in the
basement and you need to hire new sysadmins. These hostile parties would
pretty much own your site.
This rates with the older question "Is it safe to put a connection string in
the global.asa under ASP Classic?" If someone can actually get into the
directory structure to get that connection string out, they probably already
own my machine, they are in as an admin, and they can get into my database
(whether its on a remote machine or local).
Strict security practices and ensuring they are adhered to religiously is
your best protection.
Of course, I could be wrong, but that's just my two cents worth.
DJ
"ss*******@gmail.com" wrote:
You're right.
But, even if someone does have domain rights to the web.config doesn't
mean that should have the connection string information -- thus, it
being encrypted for that reason.