CLR在启动authenticode签名应用程序时联系crl.verisign.net [英] CLR contacting crl.verisign.net when starting authenticode signed app

问题描述

我注意到每次启动使用Authenticode签名的.NET应用程序时， CLR尝试联系CRL.VERISIGN.NET以更新已撤销证书的系统列表。

在有计算机的计算机上一个IP连接但是连接到CRL.VERISIGN.NET是不可能的（例如防火墙阻塞访问），启动时间可能需要2分钟！在某些限制互联网访问的公司中可能会发生这种情况。

由于我们的软件已通过Vista认证，我们无法删除authenticode签名，但同时，我们的客户不能接受可能需要几分钟才能启动的软件！

有没有办法告诉CLR不要联系Verisign revokation列表？

PS：使用authenticode签名的Win32应用程序不会发生此问题。这是框架带来的另一个非常恼人的问题！

解决方案

你有没有得到解决方案？

我试着禁用crl.versisign.com上的证书查找，但它不起作用...
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/0c08d268-1634-4486-8382-b735e295b3aa.mspx？ mfr = true


有没有onyone信息或解决方案？

感谢Eckhard Schulz

 

I have noticed that each time I am launching a .NET application signed with Authenticode, the CLR tries to contact CRL.VERISIGN.NET for updating the system list of revoked certificates.

 

On computers having an IP connectivity but where connecting to CRL.VERISIGN.NET is impossible (firewall blocking access for example), the launch time could take up to 2 minutes ! This may happen in some companies where internet access is restricted.

 

As our software is Vista Certified, we can not remove the authenticode signature, but in the same time, it is not acceptable by our customers to have a software that could take minutes to launch !

 

Is there any way to tell the CLR not to contact the Verisign revokation list ?

 

PS: This problem does not happen with Win32 app signed with authenticode. This is another very annoying problem brought by the framework !

解决方案

Did you get a solution ?

Well I try to disable the Cert lookup on crl.versisign.com but it doesn´t work...
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/0c08d268-1634-4486-8382-b735e295b3aa.mspx?mfr=true


Had onyone information or solution ?

Thanks
Eckhard Schulz

这篇关于CLR在启动authenticode签名应用程序时联系crl.verisign.net的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！