如果用户可以解密 web.config，那么加密它有什么意义呢？
哎呀，一些供应商告诉我的老板，不加密 web.config 是一个很大的安全漏洞。这对我来说听起来像是废话。我的意思是，如果有人破坏了服务器，我们不是就完蛋了吗？
Oi, some vendor is telling my bosses that not encrypting the web.config is big security hole. This sounds like bunk to me. I mean, if someone compromises the server aren't we screwed anyways?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
就像 @Joelt 所建议的那样，ASP.NET 最近出现了一个安全问题，允许人们访问根 Web 等中的文件。现在，这个问题可能已经存在很长时间了。或者，现在可能存在一个秘密缺陷，除了一些利特朋克之外没有人知道……这意味着我们现在都很脆弱。我的意思是，直到 ASP.NET 团队（以及他们之前一两周的安全人员）宣布之前的缺陷……这个缺陷出现了多久？有多少人利用了它？
所以——这就是总体思路。如果由于某种原因存在缺陷 - 人们可以远程访问文件 - 包括 web.config - 那么你的数据可能会被知道。
现在 - 关键是这个。所以..有人可能会发现我的数据库名称、数据库IP地址和数据库密码..对吗？但他们需要访问我的内部数据库......祝你好运。但是，我的 web.config 中可能有我的 Twitter 用户名密码吗？ （叮！灯刚刚亮）。我的第 3 方 api 用户名/密码。等等。
这就是真正的安全问题所在，IMO。
如果你知道我公司的 Twitter 用户名/密码，然后开始破坏我们的 Twitter 帐户，我会讨厌它。
Like @Joelt suggested, ASP.NET had a security issue semi recently that allowed people to access files in the root web etc. Now, this issue could have existed for a long time. Alternatively, there could be a secret flaw right now that no one knows about except some leet punks ... which means we're all vulnerable right now. I mean, until the ASP.NET team (and security people a week or two before them) announced that previous flaw ... how long was that out in the wild? How many people exploited that?
So - that's the general idea. If for some reason a flaw exists - where people can remotely gain access to files - including web.config - then your data could be known.
Now - the kicker is this. So .. someone might find out about my DB name, DB ip addy and DB password .. right? but they need to access my internal DB ... so good luck there. BUT, my web.config might have my twitter username password in there? (Ding! light just turned on). My 3rd party api username/passwords. etc.
THAT is where the real security issue lies, IMO.
I'd hate it if u learn my companies twitter username/password and then start defacing our twitter account.
加密并不意味着您受到保护。解密所需的私钥存储在服务器上，因此如果您的服务器遭到破坏，您的 web.config 可以被解密。
我们仅加密 web.config 的连接字符串部分。它有助于防止其他窥探者轻松访问我们的连接字符串，尤其是在开发环境中（通常比生产环境安全性低得多）。
加密只是分层安全的一小部分。它绝不是保护敏感信息的最终解决方案。
The encryption does not mean that you are protected. The private key needed for decryption is stored on the server, so if your server is compromised your web.config can be decrypted.
We only encrypt the connection string section of the web.config. It helps prevent other prying eyes from easily accessing our connection strings especially in the development environment (which is often much less secure than your production environments).
The encryption is just a small piece to the layered security. It is by no means an end-all solution for protecting your sensitive information.
ASP.net 中最近发布了一个安全漏洞，该漏洞允许远程用户访问 Web 根目录中的任何文件（包括 web.config），而无需访问整个服务器。此外，web.config 中可能存在允许危害一台服务器而危害另一台服务器的登录信息。
There was a recently released security hole in ASP.net that would have allowed a remote user to access any file in the web root, including web.config, without accessing the entire server. Additionally, there may be login information in the web.config that allows compromising one server to compromise another.
有点像。就我而言，我托管在共享托管帐户上。所以很多人都可以访问我的帐户和存储在那里的文件。
就我个人而言，我并不太担心。但是，如果有人愿意，他们就可以访问该信息。即使您拥有服务器，如果它是一家公司，那么可能会有很多人可以访问它。
对于关键数据，对其进行加密是有意义的。
Sort of. In my case, I host on a shared hosting account. So a lot of people have access to my account and the files stored there.
Personally, I don't worry about it too much. But, if someone had a mind to, they could access that information. And even if you own the server, if it's a company then there could be a lot of people who have access to it.
For critical data, encrypting it makes sense.