.NET DLL使用不同的TLS版本
我们有一个Microsoft Access应用程序,可在eBay上合并我们的许多活动。我通过几个访问参考的com dll来做到这一点。从我们的库存到eBay的申请帖子列表的一部分。这已经工作至少8年了。最近,eBay更改了它的服务器需要TLS 1.2,我们开始获得“请求中止:无法创建SSL/TLS安全频道”消息。抬起头,MS说,将DLL项目升级到框架4.7或更高版本将修复。我升级了解决方案框架并重新编译。
当我从VS内置的Win表单测试应用程序中调用eBay时,升级的DLL可以使用eBay。当我从访问应用程序打电话时,我仍然会收到TLS错误。当我在Fiddler中查看与eBay的通信时,当来自.NET WIN表单测试应用程序使用TLS 1.2时,来自DLL的呼叫。当从访问中调用DLL时,它仍在使用TLS 1.0。访问应用程序和.NET测试应用程序都引用相同的DLL文件。
问题:调用DLL的应用程序是否会影响所使用的TLS版本?关于什么可能导致同一DLL使用不同的TLS版本的想法?
We have a Microsoft Access application that consolidates many of our activities on eBay. I do this through several com dll's that Access references. One part of the application posts listings from our inventory to eBay. This has been working for at least 8 years. Recently eBay changed it's servers to require TLS 1.2 and we started getting "The request was aborted: Could not create SSL/TLS secure channel" message. Looked this up and MS says upgrading the dll project to Framework 4.7 or later will fix. I upgraded the solution framework and recompiled.
The upgraded dll works with eBay when I call from a win forms test application built in VS. When I call from the Access application I still get the TLS error. When I looked at the communications with eBay in Fiddler the calls coming from the dll when called from the .NET win forms test app use TLS 1.2. When the dll is called from Access it is still using TLS 1.0. Both the Access app and the .NET test app reference the same dll file.
Question: does the application calling a dll influence the TLS version being used? Any ideas on what could be causing different TLS version being used by the same dll?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
哼,我认为VBA/办公室是主机计划会改变TLS设置。但是您可以考虑尝试此注册表编辑:
我相信您还必须重新启动您的计算机才能生效。
Hum, I did not think that VBA/Office being the host program would change the TLS settings. But you could consider trying this registry edit:
I believe you also have to re-start your computer for above to take effect.