blocks|key|3297246|text|使用WCF，您可以在消息级别使用密码凭据，在传输级别使用SSL，我认为在您的情况下这就足够了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3297247|参见here。|offset|length|3297248|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms733836.aspx?ppud=4^0|0|2|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Well, with WCF you could use Password credential at message level and SSL at transport level, which I think would be enough in your case.

See <a href="http://msdn.microsoft.com/en-us/library/ms733836.aspx?ppud=4" rel="nofollow noreferrer">here</a>.

blocks|key|3083943|text|如果您想加密传输中的消息(这真是一个好主意！)，发送者(客户端)和服务器之间必须有一些共享的知识。这可以是硬编码的，但这真的不是一个好主意--如果“公共共享”知识被泄露，攻击者就可以破译和阅读你的所有消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3083944|此外，由于这绝对是而不是推荐的做法，所以在WCF中没有任何类型的支持来简化共享密钥的使用。你要靠你自己--你必须100%25靠自己。|offset|length|style|BOLD|3083945|以安全的方式交换公共共享秘密的唯一可行的方法是使用证书。别无他法，抱歉。证书甚至不必用于用户身份验证或任何东西-但它在调用者和服务之间建立了一个共享的秘密，从而允许调用者以只有目标接收者才能实际解密和使用的方式加密消息。|3083946|所以我真的看不出有什么方法可以在你的服务器上安装证书--不需要在每个客户端上，而是在你的服务运行的每一个服务器上。|3083947|Marc|3083948|PS:如果你真的想要研究“硬编码的共享密钥”方法，你需要考虑一下：|3083949|3083950|如何在每个客户端上安全地存储共享密钥？|unordered-list-item|3083951|如何使用存储的共享密钥中的信息对消息进行加密？|3083952|3083953|通常，这种方法有两个方面：|3083954|3083955|交换某种形式的私钥/公钥对；服务器生成密钥对并将私钥保留给自己，并与客户端共享公钥(例如，通过WCF消息，对于私钥/公钥对，交换公共共享密钥，例如，将对称加密您的消息的“加密密钥”(并且由于它是对称的，服务器可以使用相同的密钥来解密您客户端上的messages)|ordered-list-item|3083956|setup基础设施(例如，称为行为的WCF扩展)，以便在消息发出之前对其进行检查，并使用您的共享密钥|3083957|对其进行加密|3083958|总而言之，它真的不是微不足道的--任何比这更简单的东西都不值得被称为“安全性”。|3083959|如果您查看所有必须完成工作-只使用WCF内置证书机制不是更容易吗？|3083960|正派的安全性值得它的盐是硬的-所以为什么不利用可用的东西，而不是自己做所有的工作，或者更糟:想出一个半生不熟的解决方案，它很容易破解，你可以很容易地以明文发送所有东西.不要低估了处理最基本的安全场景所需的代码的复杂性和数量-+WCF为您做了所有这些-免费，以可靠和安全的方式-使用它！你不会后悔的！|3083961|entityMap^0|0|9|3|0|F|2N|0|0|1L|0|0|4|0|0|X|0|0|0|J|0|0|N|0|0|0|D|0|0|0|3N|0|0|1E|0|0|6|0|0|14|0|0|X|0|0|45|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1L|8|@$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1O|8|@$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1R|8|@$D|1S|E|1T|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1V|8|@$D|1W|E|1X|F|G]]|9|@]|A|$]]|$1|T|3|U|5|S|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|22|8|@$D|23|E|24|F|G]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|Z|3|10|5|11|7|26|8|@$D|27|E|28|F|G]]|9|@]|A|$]]|$1|12|3|13|5|11|7|29|8|@$D|2A|E|2B|F|G]]|9|@]|A|$]]|$1|14|3|15|5|6|7|2C|8|@$D|2D|E|2E|F|G]]|9|@]|A|$]]|$1|16|3|17|5|6|7|2F|8|@$D|2G|E|2H|F|G]]|9|@]|A|$]]|$1|18|3|19|5|6|7|2I|8|@$D|2J|E|2K|F|G]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2L|8|@$D|2M|E|2N|F|G]]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]]|1D|$]]

If you want to encrypt the messages on the transport (which is a really good idea!), there has to be some shared knowledge between the sender (the client) and the server. This can be hardcoded, but that's really not a good idea at all - if that "common shared" knowledge is ever compromised, an attacker could decipher and read all your messages.

Also, since it's definitely not recommended practice, there's no support of any kind in WCF to simplify using a shared secret. You're on your own - you have to roll your own 100% of the way. 

The only viable way to have a common shared secret exchanged in a safe way is to use a certificate. No way around this, sorry. The certificate doesn't even have to be used for user authentication or anything - but it establishes a shared secret between the caller and the service and thus allows the caller to encrypt the messages in such a way only the intended recipient can actually decrypt and use them. 

So I really don't see any way you can get around having certificates on your servers - doesn't need to be on every client, but on every server where your service runs.

Marc

PS: if you really want to investigate the "hardcoded shared secret" approach, you'll need to think about this:

<ul>
<li>how do you store a shared secret safely on each and every single one of your clients?</li>
<li>how do you use information from that stored shared secret to encrypt your messages?</li>
</ul>

Typically, the approach would be two-fold:

<ol>
<li>exchange some form of a private/public key pair; the server generates a key pair and keeps the private key to itself and shares the public key with the client (e.g. over a WCF message, for instance)</li>
<li>using that private/public key pair, exchange a common shared secret, e.g. an "encryption key" that will symmetrically encrypt your messages (and since it's symmetrical, the server can use the same key to decrypt the messages)</li>
<li>setup infrastructure on your client (e.g. a WCF extension called a behavior) to inspect the message before it goes out and encrypt it with your shared secret</li>
</ol>

All in all, it's really not trivial - anything simpler than that is not worth being called "security" at all. 

If you look at all that work you will have to do - wouldn't it be easier to just use the WCF built-in certificate mechanisms??

Decent security worth its salt is hard - so why not leverage what's available instead of doing all the work yourself, or worse: come up with a half-baked solution that's so easy to crack you could just as easily send everything in cleartext..... don't under estimate the complexity and amount of code needed to handle even the most basic security scenarios - WCF does this all for you - for free and in a reliable and safe manner - use it! You won't regret it!

blocks|key|330881|text|对于消息安全性，您的客户端提供一些凭据，服务器提供一些凭据。对于此设置和您的场景，您可以不使用带有Custom+Username+Validator的客户端用户名和密码以及服务器证书来提供服务器凭据。此Application+Scenario提供了实现此目的所需的配置设置，但aspNet+membership部分除外，您必须将其替换为自定义验证配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|330882|您的服务器上仍然需要有效的证书(客户端上不需要证书)，但我看不出有任何方法可以解决这个问题。|330883|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa702565.aspx|1|http://wcfsecurity.codeplex.com/wikipage?title=Internet%2520%25u2013%2520Windows%2520Forms%2520Client%2520Calling%2520WCF%2520Using%2520Message%2520Security&referringTitle=Application%2520Scenarios^0|1D|P|0|2T|K|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

For message security, your client provides some credentials and server provides some credentials. For this setup and with your scenario could you not use the client username and password with a <a href="http://msdn.microsoft.com/en-us/library/aa702565.aspx" rel="nofollow noreferrer">Custom Username Validator</a>, and a server certificate to provide the server credentials. This <a href="http://wcfsecurity.codeplex.com/wikipage?title=Internet%20%u2013%20Windows%20Forms%20Client%20Calling%20WCF%20Using%20Message%20Security&amp;referringTitle=Application%20Scenarios" rel="nofollow noreferrer">Application Scenario</a> provides a fair chucnk of the configuration setup you would need to achieve this, except the aspNet membership sections, which you would have to replace with your custom validation config.

You would still need valid certificates on your servers (no certificates required on the clients), but I can't see any way around this.

blocks|key|327542|text|看看下面的示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|327543|http://www.codeproject.com/KB/WCF/wcfcertificates.aspx|offset|length|327544|它使用证书，但没有证书存储-因此不需要设置。|327545|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1I|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

Take a look at the following sample:

<a href="http://www.codeproject.com/KB/WCF/wcfcertificates.aspx" rel="nofollow">http://www.codeproject.com/KB/WCF/wcfcertificates.aspx</a>

It uses certificates but without a certificate store - so no setup is necessary.

blocks|key|3083996|text|嗯..。也许可以使用一些简单的东西。将加密从软件转移到硬件。从每个客户端网络到您自己的VPN，然后您可以为WCF传输做任何您喜欢的事情。该行不是明文，问题就解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3083997|当然，这说起来容易做起来难，但大多数网络供应商都提供了相当简单的VPN配置，而且这可能比尝试为SSL证书开发安装程序和配置客户端更容易。|3083998|我希望它能有所帮助！|3083999|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Hmm.. maybe something simple could be used. Move the encryption from software to hardware. VPN from each client network to your own and then you can do whatever you like for WCF transport. The line is not clear text and the problem is solved.

Of course this is easier said than done, but most network vendors provide a pretty easy VPN config and it maybe easier than trying to develop an installer for SSL certs and configure the client.

I hope it helps!

I have a WCF service and client which is going to be deployed to several companies (hundreds). Some companies will run the software in their network and some will run it over the Internet (WCF server at on office, WCF client at another).

We want to encrypt the communication between the WCF server and client. We don't have any need to authenticate the cient / subscriber using WCF security, because we have our own username/password log-in which the clients will use to log on the server.

<ul>
<li>We can't rely on Windows auth because some of the users will run it over the Internet, and the WCF server may not be on the same domain as the WCF client.</li>
<li>If we use "real" certificates*, companies running the software would have to purchase certificates from a CA and install it, and then configure our software to use it, but this is too complicated for most of them.</li>
<li>We could auto-create certificates during installation of the WCF server, but then we would have to automatically install it into a certificate store and somehow automatically grant IIS permissions to read the certificate. This is more complicated than we would like.</li>
</ul>

In short, we want a simple solution where the encryption is just based upon a shared secret, in our case the username / password the user is logging on with. I do understand that this won't give the best available encryption, but we're willing to trade some of the security to make the software easier to deploy.

Is this possible?

*With "real" certificates, I mean certificates purchased from a certificate authority, and not one I've created myself / self-signed.

WCF message security without certificate and windows auth

身份验证

对称加密

服务器

Windows

我有一个WCF服务和客户端，这将部署到几个公司(数百)。一些公司将在他们的网络中运行软件，一些公司将在互联网上运行它(WCF服务器在办公室，WCF客户端在另一个)。我们希望对WCF服务器和客户端之间的通信进行加密。我们不需要使用WCF安全来验证有效/订阅者，因为我们有自己的用户名/密码登录，客户端将使用它来登录服务器。...

问没有证书和windows身份验证的WCF消息安全性
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问没有证书和windows身份验证的WCF消息安全性EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问没有证书和windows身份验证的WCF消息安全性
EN