出于安全原因，我应该在 WCF 中使用 NetNamedPipe 绑定吗？
WCF 文档称“网络命名管道”绑定可用于单台计算机上的快速进程间通信。它不能用于跨机器通信。
我想知道使用网络命名管道绑定是否可以保护我的服务免受来自网络外部的攻击。有人告诉我，答案是否定的。虽然网络命名管道绑定旨在用于同一台计算机上的进程间通信，但它可以被黑客攻击以允许从其他计算机进行访问。准确吗？
WCF 专家请插话。使用网络命名管道绑定是否能从本质上保护我的服务免受来自其他计算机的未经授权的访问？
The WCF documentation says that the "Net Named Pipe" binding can be used for fast interprocess communication on a single machine. It cannot be used for communication across machines.
I would like to know if using the Net Named Pipe binding will protect my service from being attacked from outside the network. I've been told that the answer is no; that although Net Named Pipe binding is meant to be used for interprocess communication on the same machine, it can be hacked to allow access from other machines. Is that accurate?
WCF experts, please chime in. Does using the Net Named Pipe binding intrinsically protect my service from unauthorized access from other machines?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
正确的答案是肯定的：NetNamedPipeBinding 从本质上保护服务免受来自网络上其他计算机的任何访问。 WCF 服务端堆栈创建的管道带有一个 ACL，该 ACL 拒绝对具有 NETWORK USERS 组成员身份的任何登录令牌的所有访问。此组成员身份存在于任何网络登录令牌中。
NetNamedPipeBinding 存在一些安全问题，特别是在 .NET 3.5 中，但远程攻击漏洞并不是其中之一。
请参阅这篇文章和后续文章了解详细信息。
The correct answer is YES: the NetNamedPipeBinding does intrinsically protect the service from any access from other machines across the network. The pipe which the WCF service-side stack creates carries an ACL which denies all access to any logon token which has membership of the NETWORK USERS group. This group membership is present in any network logon token.
There are some security issues with the NetNamedPipeBinding, particularly in .NET 3.5, but vulnerability to remote exploits is not one of them.
See this post and subsequent posts for details.
根据名称 Net Named Pipe，此绑定使用本地命名管道作为传输机制。在 Windows 计算机上，命名管道被视为文件...因此可以远程访问，就像使用 \\machinename 浏览计算机一样。因此，由于远程计算机可以访问传输机制，因此绑定本质上无法避免未经授权的访问，尽管与 TCP 或 HTTP 相比，命名管道可能具有一些安全优势。
Per the name Net Named Pipe this binding uses local named pipes as the transport mechanism. On Windows machines named pipes are treated like files... and as such are accessible remotely like browsing to a machine with \\machinename. Therefore since the transport mechanism is accessible to remote machines the binding is inherently not immune to unauthorized access, although there may be some security advantages to named pipes as opposed to TCP or HTTP.