Strong Name (3) The vulnerability of strong names

Through the previous experience of the strong name on the assembly's protection methods and principles, but the intensity of this protection is how much? Can you effectively defend against malicious tampering? Let's look at the example below.

Return to code listing 9-7 of the previous article, strongnamereferencelib the project with a strong name signature, and then compile the StrongName project. There are StrongNam.exe and StrongNameReferenceLib.dll two files in the bin directory of the StrongName project, and then use ILDASM to open StrongNameReferenceLib.dll files, dump them as il files, and use the chronicle here This opens the Il file, as shown in Figure 9-19.

Figure 9-19 StrongNameReferenceLib.dll il source

Three codes were found in the. Il file: Publickkeytoken, PublicKey, and hash, deleting the corresponding content, and then using ILAsm to compile, when the strong name of the assembly was successfully removed.

The strong name method for replacing an assembly is essentially the same. There are a number of tools for removing and replacing strong names on the network, which are no longer demonstrated here.

Author: Hyun-Soul

Source: http://www.cnblogs.com/xuanhun/

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/net/