签名.NET程序集 [英] Signing .NET assemblies
问题描述
我试图让正式签署.NET的DLL /组件的把握。
I'm trying to get a grasp of formal signing of .NET dlls/assemblies.
在特别
- 在何时以及如何使用私钥
- 的私钥创建/控制最佳做法
- 在什么样的模块需要签名/最佳实践绕了
推荐答案
请参阅使用强名称签名,获取有关签署一个很好的文章。
See Using Strong Name Signatures for a very good article on signing.
如果我们说的组件,然后签署应该用于prevent第三方的欺骗你的code的强命名。强名称为您的程序集的一部分,因此具有相同的名称和签名不同的另一个组件是一个不同的组件。这也prevents组件被修改并重新签署(没有私钥)。
If we are talking strong naming of assemblies then signing should be used to prevent a third party from "spoofing" your code. The strong name is part of your assembly so another assembly with the same name and a different signature is a different assembly. This also prevents assemblies from being modified and re-signed (without the private key).
要成为有用的,私钥必须保密。这通常是通过href="http://msdn.microsoft.com/en-us/library/t07a3dye.aspx" rel="nofollow">延迟签名,精心管理的私有密钥访问
To be useful, the private key must be kept private. This is usually done through delayed signing and careful management of private key access.
您也可以使用 Authenti $ C $ Ç(签上你强命名程序集);这可以增加约谁大会实际上是从信心。
You can also use Authenticode (to sign your strong named assemblies); this can add confidence about who the assembly is actually from.
这篇关于签名.NET程序集的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!