The currently released Rapidtier is a beta version, completely free! Now I am developing the official version of Rapidtier, the function will have a large increase, intend to walk the way of sharing software. So now I want to find a way to protect the .NET assembly, create a complete software registration mechanism.
Today
The code project see an article on the protection .NET assembly, the author has written 3 parts (not written yet
Everyone is coming to pay attention:
Building security awareness in .NET Assembly: Part 1 - Learn to Break a .net assembly
Building security awareness in .net assembly: Part 2 - Learn To Protect Your .net assembly from behing tampered
BUILDING Security Awareness in .NET Assembly: Part 3 - Learn To Break Strong Name .NET Assembly
I often heard it before.
Strong Name can protect the .NET assembly to prevent tampering. At that time, I didn't get in this regard, so I sounded very good. Some time I heard that someone said that after using the ILDASM to compile the IL source code, you can delete the strong name directly, modify the IL and re-sign the ILASM and re-sign. This understands that the name is that it simply acts as a unique identity assembly, and cannot protect the assembly from being tampered.
If you protect our .NET assembly? I hope that you will participate in the discussion!
