CliSecure 5.2.0.2

CliSecure is a tool that protects the IL code stored in your assemblies. It's unique in its protection strategy compared with other code protection tools, which encrypt a whole assembly that gets decrypted at runtime. They often wrap the entry point assembly (that is the one containning the entry point of the application) with a native image loader. Metadata information such as class, method names and other symbol information is not visible and can't be viewed using standard .NET tools.

Evidently, the .NET framework understands only assemblies that comply with the CLI (common language infrastructure) standard.
This means that eventually the code has to be deciphered in order for the .NET runtime to execute it. Once the application is executed the code gets decrypted by the native image loader and it resides in-memory in its decrypted form, now it is ready for the .NET runtime to work against.

This raises a factor that most code protection tools fail to cope with. Once the code is deciphered it's completely exposed to prying eyes of a potential hacker in-memory, because the entire assembly loads into memory in its MSIL form. This poses a security threat since once the assembly loads in-memory it can be dumped to a file using standard memory dump tools.

CliSecure never keeps your MSIL code decrypted at runtime, it binds to the jitter and hands it the code for execution just before compilation occurs. The execution engine assures that at most a single method will reside in memory in its decrypted form in any given time.
This makes it impossible to reconstruct your original assembly by using memory dump tools. Our tool doesn't use a native image loader that wraps around the entry assembly, this is why you can use it to deploy ASP.NET web based applications. Metadata information remains intact and can be viewed using standard .NET tools. This makes our tool perfect for distributing 3rd party library components.

On top of that CliSecure lets you obfuscate your metadata information, if you decide to do so. The obfuscation process renames metadata symbols (class, interface, field and method identifiers) to render them meaningless, and strips all unnecessary information (local variable, method parameter names, debug information and some metadata) from your .NET assemblies. This feature is offered for free and is included in the trial version of the product.

Requirements:	No special requirements
Release Date:	January 02, 2013
Platforms:	WinXP, Windows Vista, Windows Vista x64, Windows 7, Windows 7 x64
Keyword:	Code,  Code Protector,  Decoder Library Component,  File Encrypter,  Protect,  Protector
Users rating:	0/10