A .NET code protection system that secures your .NET applications or libraries and adds additional layers of protection, including obfuscation

Written by Cristina Jitaru on December 9th, 2013


Developing and compiling applications using platforms that support .NET (for instance, Visual Studio) you surely know that protecting your assemblies, classes and attributes becomes an important aspect that concerns most of the developers.

.NET Reactor is a comprehensive and reliable code protection and software licensing system specially intended for software who are written using .NET scripts.

Not to be confused with an obfuscator program; it is important to understand that .NET Reactor is an application that keeps the original .NET code intact, well protected by native code and invisible from prying eyes.

Before using .NET Reactor you must know which are the main differences between an obfuscator utility and this program. Actually, the obfuscation is the process of making your source code more difficult (though not impossible) for humans to understand.

In such a manner, you can change the meaningful names of classes, methods or variables with devious ones that are confusing and difficult to remember, but have no effect on the .NET Framework interpreter.

Still, when using apps like .NET Reactor, you can wrap your intellectual property in more layers of protection, denying access to your code by creating a native code wall between hackers and your .NET assemblies and producing a file which cannot be understood as CIL (Common Intermediate Language).

Considering the main purpose for which .NET Reactor was designed, the main window is very intuitive and user-friendly. The panel consists of four tabs, namely Files, Settings, License Manager and .NET Inspector.

That being said, you can add your main assembly and set additional files if you want to protect more than one assembly at the same time by accessing the Files tab, then go to the ‘Actions’ menu and choose the task you want.

By accessing the second tab, you can enable compression, visual styles, target file location and pre-JIT methods effortlessly.

Navigating to the ‘License Manager’ tab you can distribute your assembly without a license file, provided that you have set ‘Run without license file’ option to True. In case a client purchases a license, you can use this tab to build a license file in order to unlock your application.

Finally, the last tab, namely ‘.NET Inspector’ displays extractable information from the current assembly.

Additionally, advance license utilities can be accessed from the Tools menu of the application, speaking of ‘License Invalidation Tool’, ‘License Examiner’ or ‘Stack Trace Deobfuscator’.

To sum things up, .NET Reactor provides you with simple and reliable ways to secure .NET applications and libraries, replace CIL code with native code and protect your revenue by enforcing trial version restrictions to your apps.

.NET Reactor description

Here are some key features of ".NET Reactor":
· NET code & resource protection
· .NET code encryption
· .NET 1.1, 2.0, 3.0, 3.5 & 4.0 (Beta) assembly support
· .NET Compact Framework 1.0, 2.0 & 3.5 protection support
· ASP.NET support
· Anti ILDASM
· Mono assembly support
· Advanced licensing system
· String encryption
· Merge assemblies into one executable or library
· Removes IL code
· Native Exe file generation
· Compression support for executable files
· Protection against disassembling and hacking
· Protects any kind of .NET assembly
· ShareIt Module Generator
· Command Line support
· Intuitive GUI (Graphical User Interface)
Requirements:
· NET Framework
Limitations in the trial version:
· nag screen
What's New in This Release: [ read full changelog ]
· Improved NecroBit protection
· Improved string encryption
· Improved resource encryption and compression
· Improved 'Inject Invalid Metatada' feature
· New internal encryption algorithms to prevent static analysis by decompiler/deprotector
· Fixed issue failing Windows Store Apps certification
· Fixed issue affecting MarshalAsAttribute using UnmanagedType.SafeArray as paramter
· Fixed control flow obfuscation issue
· Fixed Anti ILDASM problem in case the base type of a class is SafeHandle
· Fixed bug affecting unhandled exception handlers
· Fixed minor bugs
· [Download]

http://www.softpedia.com/dyn-postdownload.php?p=14937&t=0&i=1

[培训]内核驱动高级班，冲击BAT一流互联网大厂工作，每周日13:00-18:00直播授课