简体   繁体   English

Windows Server 2003到2008 sslstream没有通用算法

[英]Windows Server 2003 to 2008 sslstream No Common Algorithm

I found my issue with the previous question I asked. 我发现了我之前问的问题。

It appears as though when connecting between Windows Server 2003 and 2008 using SSLSTREAM in C# the servers are not able to agree on a common algorithm. 似乎在C#中使用SSLSTREAM在Windows Server 2003和2008之间进行连接时,服务器无法就通用算法达成共识。

The exact SSPI Exception I get is: 我得到的确切的SSPI异常是:

"The client and server cannot communicate, because they do not possess a common algorithm"

I have tried using SSL2, SSL3, TLS1. 我尝试使用SSL2,SSL3,TLS1。 I tried using Default, I tried installing the AES SSL hotfix for server 2003. It seems no matter what I do, there are no common algorithms.. 我尝试使用默认,尝试为服务器2003安装AES SSL修补程序。似乎不管我做什么,都没有通用的算法。

Does anyone know how I can solve this? 有谁知道我该怎么解决?

Also, when I try the same code on Windows 7 The Server/Client agree on: Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) 另外,当我在Windows 7上尝试相同的代码时,服务器/客户端也同意: Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)

That was taken from wireshark. 那是从wireshark获取的。

Windows Server 2003 does not have that cipher, but it should have some that are compatible without having to enable the ones listed here: Windows Server 2003没有该密码,但是它应该具有一些兼容的密码,而不必启用此处列出的密码:

http://technet.microsoft.com/en-us/library/cc766285(WS.10).aspx http://technet.microsoft.com/en-us/library/cc766285(WS.10).aspx

Thanks for any help 谢谢你的帮助

I cannot figure out from your question which side is the server and which is the client, and maybe it doesn't matter. 我无法从您的问题中弄清楚哪一方是服务器,哪一方是客户端,也许没关系。 Although I'm not that familiar with those servers, I have seen similar errors when the server is not able to find its RSA private key, either due to misconfiguration or more often misunderstanding. 尽管我不太熟悉这些服务器,但是由于配置错误或更经常是由于误解而导致服务器无法找到其RSA私钥时,我看到了类似的错误。 The server must have access to both a private key and its matching public key (contained in its certificate) in order to complete an authenticated connection. 服务器必须能够访问这两个私钥和以完成身份验证的连接其对应的公钥(包含在其证书中)。

The server likely tried to negotiate a SSLv3.0 connection with an AES cipher. 服务器可能试图与AES密码协商SSLv3.0连接。 That combination is technically illegal. 从技术上讲,这种组合是非法的。 See http://blogs.msdn.com/b/ieinternals/archive/2009/12/08/aes-is-not-a-valid-cipher-for-sslv3.aspx?Redirected=true 参见http://blogs.msdn.com/b/ieinternals/archive/2009/12/08/aes-is-not-a-valid-cipher-for-sslv3.aspx?Redirected=true

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 WPF应用程序无法在Windows Server 2003/2008中工作 - WPF application not working in windows server 2003/2008 仅在Windows 2003 Server上指定了无效的算法 - Invalid algorithm specified on Windows 2003 Server only 客户端和服务器无法通信,因为它们在Windows Server 2008 Web上不具有通用算法 - The client and server cannot communicate, because they do not possess a common algorithm on Windows Server 2008 Web 从Windows Server 2008访问Windows Server 2003共享文件夹 - Access windows server 2003 share folder from windows server 2008 客户端和服务器无法通信,因为它们没有通用的算法C#SslStream - The client and server cannot communicate, because they do not possess a common algorithm, C# SslStream SSLStream.AuthenticateAsServer “客户端和服务器无法通信,因为它们没有通用算法” - SSLStream.AuthenticateAsServer “The client and server cannot communicate, because they do not possess a common algorithm” 使用C#向Windows Server 2003/2008中的防火墙添加例外 - Adding exception to firewall in Windows Server 2003/2008 using C# 在sql server 2008中从C#中选择,在Windows Server 2003中太慢了:( - Select from C# in sql server 2008 too slow in windows server 2003 :( 在Win 2003/2008服务器上运行的任务调度程序:Windows服务还是替代? - Task-scheduler running on Win 2003/2008 server: windows service or alternative? 使用在 Windows Server 2008 上运行的 C# 在 Exchange 2003 中创建邮箱 - Create mailbox in Exchange 2003 using C# running on Windows Server 2008
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM