Official website: http://www.dnguard.net/index.aspx
Official Blog: http://www.cnblogs.com/rick/ (Long time no update)
Original http://www.anqn.com/jiamijiemi/gongjujiqiao/2009-12-22/a09121848.shtml
DNGuard HVM is a .NET code security protection product that provides a strong protection solution for your .NET software product code and copyright protection. DNGuard's strong encryption, obfuscation functions, and HVM virtual machine protection functions protect your products at the same time, further protecting your legitimate interests from criminals, and it can perfectly protect your source code from decompilation and cracking without any adjustments to the source code.
Product Preview:
Technical advantages:
One of the issues that must be considered when developing .NET software products is how to protect code from reverse cracking. The technology of reverse engineering access to code has been around for a long time, and in fact, .NET assemblies contain IL code and rich metadata that can be easily cracked, illegally modified, and recompiled. For developers who want to protect their intellectual property, this effortless crack poses a very important security issue.
Lutz Roeder's Reflector, Microsoft's ILDASTM and other .NET decompilers can easily view your assembly's IL code, so that your source code can be learned by people with ulterior motives who can recompile your software product into a personal version, and your intellectual property is not protected.
DNGuard Pro encrypts the IL code of your assemblies to protect your intellectual property. When the encrypted assembly runs, it is decrypted and compiled by the just-in-time compiler (JIT); The DNGuard parsing engine ensures that at least one method exists in memory at any given time, which ensures that there is no possibility for crackers to dump your assembly source code from memory.
DNGuard Enterprise has HVM technology that converts the IL code of an assembly into HVM pseudocode and encrypts the pseudocode to provide the best protection for your intellectual property. When the encrypted assembly runs, the HVM compiler hands over the pseudocode to the prompt compiler and helps the on-the-fly compiler compile the on-premises code directly from the pseudocode. The HVM parsing engine ensures that no IL code is present in memory at any time, which ensures that crackers have no chance of dumping your assembly source code from memory.
Code-based encryption solutions:
Code encryption uses standard encryption algorithms to encrypt MSIL code so that the decompiler cannot read the source code, preventing crackers from reverse cracking your assembly. Since the encrypted code no longer contains the MSIL structure, neither ILdasm nor other decompilers can dump the assembly. In this regard, traditional fuzzy techniques cannot be compared. However, the .NET framework can only parse standard Common Language Interface (CLI) assemblies, which means that encrypted code is eventually decrypted for execution by the .NET runtime. Most code protection tools fully encrypt the entire assembly and decrypt it at runtime; They typically use a local code loader to encapsulate an entry assembly (an assembly containing a program entry point) so that similar classes, methods, and other metadata information are not visible and cannot be viewed using standard .NET tools. However, if the program is executed, the local code loader will decrypt the code, and there will be fully decrypted code in memory for the .NET runtime to parse and run, which is something that most code protection tools don't realize about; Once the code is fully exposed in memory as an MSIL, the cracker may dump the code from memory, which also poses a security issue.
How is DNGuard different from other code protection tools?
*DNGuard ensures that your MSIL code is always encrypted, run by the .NET parsing engine at runtime, parsing only one method at a time, and your MSIL code never appears in full memory at a time.
*Our protection tool does not use a local code loader that encapsulates the entire assembly, so you can also use it to encrypt your ASP.NET web application.
*Metadata information is preserved intact and can be viewed with standard .NET tools, so third-party support components are perfectly distributed using our protection tools. Now you can give your customer a protected .NET component so that he doesn't keep your IP address when he develops his own application.
How is HVM different from each method protection tool?
HVM is a virtual machine technology that is responsible for processing only one method at a time of program code and never decrypting the method into MSIL form; It only decrypts methods into dynamic pseudocode before the HVM compilation engine compiles, helping on-the-fly compilers generate local code directly from pseudocode. The HVM parsing engine ensures that there is no full IL code residing in memory at any time.
|
Posted on 9/8/2017 5:31:53 PM
|
|
|
|
Posted on 10/18/2017 1:58:40 PM
|
