The DeployLX runtime is a library of copy protection methods that integrate into your product. Rather than writing custom rules in your code or learning an arcane list of methods to enforce different rules, you just call one method from the DeployLX Library. DeployLX CodeVeil performs a complete analysis of the entire application to identify all explicit and implicit dependencies, standard naming conventions and serialization requirements.

Code Encryption
The next level of protection with method code encryption. Ambient decryption provides just enough for the runtime to execute a method and never exposes a decrypted version of your assembly.

Smart Obfuscation
More than just renaming. Smart obfuscation and one-way name overloading ireversibly eliminate names and associations not required at runtime. Zero-width encoding erases names from disassemblers.

Active Runtime Protection
Passive protection like obfuscation and encrpyption frustrate hackers. Process an assembly with CodeVeil and it gets runtime protection that actively interferes with hacking efforts with anti-debugging, tamper proofing and runtime obfuscation.



Stop Reverse Engineering
Precision corruption of assembly meta-data and clever application of the .NET runtime specification allows CodeVeil to produce assemblies that are functionally identical but break disassembly tools like Reflector and ILDASM.

Tamper Proofing
Trust that the code you deliver is the code that runs. More than just detecting tampering, CodeVeil uses a verification process that corrupts runtime state if protected assemblies or it's third party dependencies have been modified.



Obfuscate Everything
Rename more than just private members. Obfuscate calls to everything including calls to system libraries and third party assemblies.

Additional Protection Features

String and Resource Encryption & Compression
Re-sign strong named assemblies with SNK files or from a Key Container
Support 32-bit and 64-bit applications
Windows Applications, DLL and Component Libraries, ASP.NET Applications & Controls
Support Generics across all advanced obfuscation protections



While most passive obfuscation techniques stop protecting your application once delivered, DeployLX CodeVeil remains active. Taking aggressive measures to actively interfere with the efforts of hackers to debug, tamper and reverse engineer your protected assemblies. The Runtime Executive uses innovative techniques to corrupt debugger internal structures and interfere with static code analysis.

Once you've protected your assembly and released it to your customer how can you be certain that it will remain protected? Obfuscation only tools offer no protection from later modification or memory and reflection attacks. When Code Encryption is used to protect your assembly, CodeVeil will continue to protect your application from modification or disassembly. This topic discusses some of the efforts CodeVeil takes to continue protection at runtime.

During the encryption phase of the veiling process, CodeVeil will add a native 32-bit loader to your assembly. The Runtime Executive takes over portions of the .NET runtime to decrypt your codeonly when it is needed and then destroys it. During this process and continually during execution the executive provides the following additional protections.

Anti-Modification
When your assembly is first loaded the executive uses the encrypted version of your assembly as a decryption key to decode key portions of itself. Any unauthorized modifications to the assembly will corrupt this process preventing the assembly from loading properly. When Verify assembly strong names is selected, the runtime executive will check the strong name signatures of the protected assemblies and any third party assemblies referenced by the application even if strong name verificiation is disabled on the machine.

Anti-Debugging
The runtime executive injects additional instructions that will wreak havoc on debuggers that attempt to attach to a veiled process and perform any debugging operations. CodeVeil uses many different anti-debugging techniques - some well known, others designed by XHEO - so that overcoming one block does not expose other portions of the code. Component developers should carefully consider the use of this option. When used developers using the components will not be able to debug even their own code.

Anti-Dumping
One common technique for disassembly encrypted applications is to run the application, then save the in-memory version of the application to disk. The dumped version can then be modified by the hacker and then reloaded in its decrypted state. The runtime executive decrypts only those portions of the code required for the immediate execution of the code and injects it directly into the .NET runtime memory structures. The decrypted version of the assembly is never available in memory.

Home:

http://xheo.com

[/b]

[b] Only for V.I.P

Warning! You are not allowed to view this text.