Assembly Protection RRS feed

  • Question

  • Hello,

    I have some questions regarding the protection of assemblies via Digital Signing with public/private key pairs.

    Suppose the deployed assembly is digitally signed and has its hash value and public key in its meta contents. If someone tries and manages to change the assembly logic (breaking an application protection algorithm and thus cracking the app), the CLR would not load the assembly because of the hash value mismatch. Until now it is OK but what if the cracker uses the sn.exe tool on the client machine, and instructs the CLR to skip the verification of the assembly allowing the runtime to execute it? I guess the sn.exe tool comes with the .NET Framework SDK, therefore it is its absence on most client machines that would prevent its usage for cracking purposes, but I consider its installation is not that big issue.

    So, how can I be sure that my modified assembly would not run at all, unless re-signed with my public/private key pair?



    Deyan Ginev
    Thursday, August 30, 2007 8:15 AM


  • Keep your private key in a safe place.
    Thursday, August 30, 2007 8:14 PM