One concept that Java and .NET mutually share is the use of expressive file syntax for delivery of executable code: bytecode in the case of Java, MSIL (Microsoft Intermediate Language) for .NET. Being much higher-level than binary machine code, the intermediate files are laden with identifiers and algorithms that are immediately observable and ultimately understandable. .NET ups the ante by including readable metadata that explains the intended runtime behavior of the file. Add the mechanized assistance of decompilers and you have a situation that clearly exposes intellectual property to compromise and threatens security breaches.
Organizations concerned with their intellectual property need to take a hard look at this issue when considering the .NET platform. Obfuscation is a technique that provides for seamless renaming of symbols in your assemblies as well as other tricks to foil decompilers. Properly applied obfuscation can increase the protection against decompilation by many orders of magnitude, while leaving the application intact.
Some of the feature which obsification tool provides.
Replaces names by nonsense names without affecting functionality
User definable list of preserved names
Predefined list of reserved names for .NET environment provided
Strips comments and removes most source code structure
User definable comment filtering, to preserve Copyright and other legal notices
No changes to the your C# compilation or execution procedures or environment
Option to neatly format C# source code to aid development before obfuscation.
Output encoding in ASCII, European ASCII, or UNICODE
Command line and GUI interfaces
Visual Studio 2003 & well as 2005 provides a tool called dotfuscator.exe for doing this. You can find this in Visual Studio DotNet tools.
Enjoy Obfuscation....:)
|
No responses found. Be the first to respond and make money from revenue sharing program.
|