Is signing an assembly protection against cracking?

For a .NET 2.0 winform app, is using SN.EXE along with obsfucation enough to discourage most crackers?  

How can even the most determined crackers get around those two techniques?
brettrAsked:
Who is Participating?
 
mrichmonConnect With a Mentor Commented:
>>For a .NET 2.0 winform app, is using SN.EXE along with obsfucation enough to discourage most crackers

No.  If someone wants to crack your code it is not going to do it.  In fact, they could use a free reflector and see your code in a much easier to read manner if they chose.

Signing just means that they could not modify your code then reupload it to your server, without some other changes.  It doesn't mean they can't change it.   They would just be unable to re-sign it with your key - unless they stole that somehow.  Of course if they can upload code to your server you have bigger problems than whether or not your code is signed...
0
 
AlexNekConnect With a Mentor Commented:
>Is signing an assembly protection against cracking.
With signing it is not so easy to modify the code.
With obsfucation it is not so easy to understand "reassembled" code.

Here is good article about signing, I think.
http://www.codeguru.com/columns/experts/article.php/c4643/

I personally don't know how to change signed assembly now but I believe it is possible to crack an application with digitally signed assembly.
0
All Courses

From novice to tech pro — start learning today.