How hard is it to interfere with a strong named assembly?

Question

Suppose I have a .NET assembly that has a strong name. Only I have access to the private key. Then I distribute the assembly to some client system.

How difficult is it for the customer to change the assembly? That is: what would they need to do to change my assembly?

Answer 1

A strong name does not prevent assembly modification, but prevents the unintended use of other applications that reference a strong named assembly using a modified version.

Answer 2

. , (sn.exe).

Answer 3

, .

, , - ( ) (, , ..) . , , , . , Crypto Obfuscator .