clr.sll!StrongNameSignatureVerification CPU 消耗
我有一个 C# (.NET 4.0) WinForm 应用程序，它持续与基于 Linux 的应用程序通信，每秒几次从中接收一些数据。当我看到“clr.sll!StrongNameSignatureVerification”正在消耗该应用程序的大量 CPU 时，我一直在微调此 WinForm 应用程序以减少其高 CPU 使用率。我使用 Process Explorer 来找出这一点。一些 Google 搜索告诉我，“clr.sll！StrongNameSignatureVerification”正在启动，因为 CLR 正在尝试验证这是否是强命名程序集（我不希望 CLR 这样做）。
经过进一步研究，我尝试了 Microsoft SDK 中的 sn.exe 来跳过此 WinForm 应用程序的签名验证。我收到一条错误消息，指出这不是强命名的程序集。 我并不感到惊讶，因为我尚未签署此应用程序，或者不记得设置了任何应调用 CLR 来验证此应用程序签名的内容。
我在 .net 应用程序安全方面的经验几乎为零，因此目前我正在寻求有关此事的帮助。任何指针都会有帮助。
提前致谢。
I have a C# (.NET 4.0) WinForm application that continuously communicates to a Linux based application, receives some data from it few times a second. I have been fine-tuning this WinForm application to reduce it's high CPU use when I saw 'clr.sll!StrongNameSignatureVerification' is consuming a lot of CPU for this application. I used Process Explorer to find this out. Some Google searching told me that 'clr.sll!StrongNameSignatureVerification' is kicking-in because CLR is trying to verify whether this is a strongly named assembly (which I don't want CLR to).
After my further research on this, I tried sn.exe from Microsoft SDK to skip signature verification for this WinForm application. I got an error saying that this is not a strongly named assembly.
I wasn't surprised as I haven't signed this application or don't remember setting anything that should invoke CLR to verify the signature of this application.
My experience in .net application security is almost zero so at moment I am looking for some help on this matter. Any pointer will be helpful.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
查看 clr.sll!StrongNameSignatureVerification 之后的偏移量，如果它大于几千字节，则可能意味着符号未加载到 Process Explorer 中，问题可能出在 clr.dll。
Look at the offset after clr.sll!StrongNameSignatureVerification, if it's larger than a few thousand bytes, it probably means the symbols are not loaded in Process Explorer and the problem might be in any other method in clr.dll.