Take Advantage of Our Advanced .NET Obfuscation Features

If you desire to completely eliminate the metadata information stored in your assemblies such as class and methods names you can do so using the obfuscation capabilities offered by our product.

 

 

Features

Entity Renaming 

protects your code from reverse engineering by replacing class, method, and field names with inexpressive characters. If afterwards the obfuscated assemblies are decomplied, it will be extremely diffcult to derive the original purpose of the obfuscated code entities. As an additional side-effect, name obfuscation will significantly reduce the size of your application, depending on the chosen renaming scheme.

Renaming scheme includes 'unreadable chars' scheme, this method will transform classes, methods and field names to unused unicode chars. When decompiled, the result is an extermly difficult to understand source code. Since unsed chars are used it won't be possible to compile the sources produced after decompilation. 

Control Flow Obfuscation

Control Flow Obfuscation hides the control flow information of the program by transforming exiting code flow patterns to semantically equivalent constructs, however different than the code originally written. The control flow obfuscation algorithm converts the original implementation into spaghetti code thus making it extremely harder to infer program logic.

Cross Assembly Obfuscation

Cross Assembly Obufscation allows renaming of external references thus dramatically increasing the number of obfuscated constructs. Given a set of assemblies that interface each other, CliSecure will rename classes, methods and fields referenced from other assemblies uniformly. For example, if class A declared in assembly A is referenced from assembly B and CliSecure renames class A to A1, it will also rename B's external reference from A to A1.

Code Shrinking

If your application does not use all of the contained MSIL code, CliSecure will drastically reduces the size of the input assembly files. The shrinking engine analyzes the MSIL code of all input files in order to determine which code entities can not be reached from a set of given code entry points. These obsolete code fragments (either entire classes or single methods and fields) will then be removed by CliSecure. 

Software Watermarking

Software watermarking is a technique used to protect software from piracy. It is used to discourage a user from illegally redistributing copies of the software. The general idea of software watermarking is very similar to media watermarking in which a unique identifier is embedded in images, audio, or videos through the introduction of errors which are undetectable by the human. A watermark can be used to identify owners of the software or to track the origin of a pirated copy.

String encryption

CliSecure secures sensitive data such as license codes, time lock expiration date, database connection strings, etc. Strings are decrypted only when they are demanded by your application code.

Configuring your obfuscation process

Declarative obfuscation using standard custom attributes allows you to enforce restriction on classes or methods that you don't wish to obfuscate or would like to ensure that they will get obfuscated. This is done by annotating your code using the System.Reflection.ObfuscationAttribute on types and their members which tells CliSecure how to obfuscate them. It will allow you to enforce a restriction on a single class or method as well as enforcing one to a class and all its members.

x64 platform support

Supports 32-bit and 64-bit applications

Framework 1.1, 2.0, 3.0, 3.5, 4.0 support

Support all versions of the .NET framework including version 4.0, the framework that ships with windows 7. Our obfuscation tool can be used to protect applications deployed under the .NET Compact Framework. 

Mixed-mode Assemblies Support

CliSecure can process mixed-mode assemblies.

MSBuild and NAnt build Integration

CliSecure integrates with MSBuild and NAnt thus promoting its usage as a part of an entire range of complex build scenarios.

Secure Software Licensing .NET Code Protection