程序集应该拥有一个有效的强名称

Assemblies should have valid strong names

TypeName:

AssembliesShouldHaveValidStrongNames

CheckId:

CA2210

Category:

Microsoft.Design

Message Level:

CriticalError

Certainty:

95%

Breaking Change:

NonBreaking

Cause: An assembly is not signed with a strong name, the strong name could not be verified, or the strong name would not be valid without the current registry settings of the computer.

Rule Description

This rule retrieves and verifies the strong name of an assembly. A violation occurs if any of the following are true:

The assembly does not have a strong name.
The assembly was altered after signing.
The assembly is delay-signed.
The assembly was incorrectly signed, or signing failed.
The assembly requires registry settings to pass verification. For example, the Strong Name tool (Sn.exe) was used to skip verification for the assembly.

The strong name protects clients from unknowingly loading an assembly that has been tampered with. Assemblies without strong names should not be deployed outside of very limited scenarios. If you share or distribute assemblies that are not correctly signed, the assembly can be tampered with, the common language runtime might not load the assembly, or the user might have to disable verification on his or her computer. An assembly without a strong name suffers from the following drawbacks:

Its origins cannot be verified.
The common language runtime cannot warn users if the contents of the assembly have been altered.
It cannot be loaded into the global assembly cache.

Note that to load and analyze a delay-signed assembly, you must disable verification for the assembly.

How to Fix Violations

To fix a violation of this rule, use the Strong Name tool (sn.exe) to create a key file and sign the assembly with a strong name using one of the following procedures:

Use the Assembly Linker tool (Al.exe) provided by the .NET Framework SDK.
For the .NET Framework v1.0 or v1.1, use either the System.Reflection.AssemblyKeyFileAttribute or System.Reflection.AssemblyKeyNameAttribute attribute.
For the .NET Framework version 2.0, use either the /keyfile or /keycontainer compiler option (/KEYFILE or /KEYCONTAINER linker option in C++).

When to Exclude Messages

Only exclude a message from this rule if the assembly is used in an environment where tampering with the contents is not a concern.

引起的原因：

1．程序集没有使用强名称进行签名

2．强名称不能被校验

3．该程序集的强名称依赖于当前计算机的设置才有效。

描述：

这个规则读取并校验一个程序集的强名称，下面任何一条都会引起这条规则校验失败：

1．这个程序集没有进行强名称签名

2．进行签名后，这个程序集被修改过。

3．程序集被设置成延迟签名

4．程序集签名失败

5．程序集需要一定的注册表设置才能通过强名称校验

例如：通过强名称工具(Sn.exe)设置跳过对这个程序集的强名称确认

强名称保护用户不会使用一个被篡改的程序集。一个没有强名称的程序集只能被使用在非常小的范围内。如果你分发一个没有进行正确签名的程序集，将不能保证它没有被篡改。如果用户没有设置忽略强名称确认，CLR将会拒绝载入这个程序集。

不对程序集进行强名称签名会有如下缺点：

1．程序集的来源将不能被保证

2．用户将无法知道程序集被篡改过

3．程序集不能被载入GAC（全局程序集缓存）

如果需要分析一个延迟签名的程序集，必须禁用这条规则。

修复：

使用强名称工具生成Key文件，并用这个文件签名程序集。你可以使用下面的一种方法签名这个程序集：

1．使用.NET Framework SDK中的程序集连接工具(Al.exe)

2．在.NET Framework v1.0或v1.1中，使用System.Reflection.AssemblyKeyFileAttribute或System.Reflection.AssemblyKeyNameAttribute属性标记程序集。

3．在.NET Framework v2.0中，使用/keyfile或者/keycontainer编译指令。（在C++中，使用/KEYFILE or /KEYCONTAINER连接指令）。