Signing lets you provide your users with a guarantee that the assembly
originated from you. When you're downloading code from the Internet or an
untrusted medium, you want to ensure that the DLL is what it says it is, and
isn't some spyware application.
If you modify the assembly, the signature will no longer be valid because
the checksum has changed.
If you choose not to authenticate then that's up to you: it's there for
people who want to ensure the source of the assembly.
Assembly signing doesn't encrypt the bytecode or make it difficult to
decompile, you want something like an obfuscator to do that.
--
John Wood
EMail: first name, dot, second name at priorganize.com
"bob" <bo**********@h otmail.com> wrote in message
news:b0******** *************** ***@posting.goo gle.com...
Hello,
I thought assembly signing might add protection against people reverse
engineering my program, removing the protection and using it
illegally.
But it seems they can just stop the clr from authenticating it with Sn
-Vr.
Is that true, or have I misunderstood?
Cheers,
Bob