RSA 加密失败,错误代码 = -2146893819
我正在编写一些代码,当另一位开发人员(也是唯一了解该系统的人)离开时,这些代码就落在了我身上。 我试图找出为什么我的客户端和服务器无法连接。 我收到以下错误:
“正版通道操作异常:连接已被强制关闭。 指定原因:RSA 加密失败,错误代码 = -2146893819”
最初的谷歌研究似乎表明 Genuine Channels 是一个正在使用的通信库(但我不确定这是否准确)。此外,似乎没有 有关该特定错误代码含义的任何信息。
如果您对可能出现的错误没有任何具体的想法,那么我可以提供
I'm working on some code that dropped on me when another developer (and the only person who knew anything about this system) left. I'm trying to figure out why my client and server are not connecting. I'm getting the following error:
"Genuine channels operation exception: The connection has been forcibly closed.
Specified reason: RSA encryption failed with error code = -2146893819"
Initial google research seems to indicate that Genuine Channels is a communications library that was being used (but I'm not sure if that's accurate). Also, there doesn't seem to be any information on what that particular error code means.
At this point, I'm fine with suggestions on where to give my research if you don't have any concrete ideas on what could be wrong.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
错误代码 -2146893819 为十六进制 80090005,在 MS 加密库中为
NTE_BAD_DATA
。这就是我在失去兴趣之前所了解的(这在我身上经常发生在加密货币方面),它只比你所拥有的更有帮助一点,所以我把它做成了社区维基。
您实际上并没有说明收到错误时您正在做什么,但 Google 上
"rsa"
和"nte_bad_data"
的热门搜索是 这个。尽管如此,它至少扩展了你的谷歌搜索词:-)
祝你好运。
Error code -2146893819 is hex 80090005 which, in the MS crypto libraries, is
NTE_BAD_DATA
.That's about as far as I got before I lost interest (that tends to happen to me a lot with crypto stuff) and it's only slightly more helpful than what you've got, so I've made it community wiki.
You haven't actually stated what you were doing when you got the error but the top hit for
"rsa"
and"nte_bad_data"
on Google was this.Still, it expands you Google search terms at least :-)
Best of luck.
供以后访问这个问题的人参考,我最终解决了这个问题。 结果是 GenuineChannels 和 GenuineChannels 版本之间的 DLL 不匹配。 我们在客户端计算机和服务器计算机上的密码学实现。
For reference to future people who visit this question, I eventually solved this issue. It turned out to be a a DLL mismatch between the versions of GenuineChannels & our cryptology implementation that were on our client machines and our server machines.