Spices.Net Obfuscator

What is Spices.Net Obfuscator?

Don't give competitors and hackers a chance to protect your code and data! Spice.Net Obfuscator is a product of the well-known family of Spices.Net. The Spice.Net Obfuscator is a .Net code protection, optimization, and protection tool that offers the wide range of technologies to completely protect your .net code and protect your data. Spice.Net Obfuscator rebuilds its .Net mounts to the new format that is impossible to disassemble, decompile, impossible to understand. .Net Obfuscator is a part of Spices.Net and offered as visual studio integrated package (Spices.VSIP.Obfuscator), standalone GUI program and as console edition. You can use Spices.Net Obfuscator as freeware for non-commercial use, all features of Spice.Net Obfuscator in the free trial are presented and work without limitations.

Why does your .Net code and data need protection?

One of the key features of Microsoft .NET is that all of its languages (c#, VB.Net, managed c++, J#) generate assemblies that contain CPU-independent instructions or so-called Microsoft Intermediate Language instructions. .NET assemblies also include metadata that describes types, members, and code references from other assemblies. At program runtime, these statements are converted to CPU-specific language by the just-in-time compiler. This architecture offers developers several benefits: it enables easy interoperability for code written in different languages, and simplifies the use of assemblies. However, there is also a major code security disadvantage: the data contained in assemblies provides enough information to retrieve the original code. This makes it difficult to protect intellectual property in an application, whose source code can be read by anyone. Developers who have spent months or years working on complex algorithms or workarounds for errors often prefer their methods to remain secret from others. That's where obfuscation can help.

Its goal is to transform a .NET mount without affecting its functionality so that it becomes difficult or impossible to decomplace. Obfuscation of .NET assemblies code with The .NET Obfuscator helps achieve four main objectives:

Protect your data Spice.Net Obfuscator removes all string data from your code to a hidden and secure location and makes it impossible to extract string information from the protected assembly. Optimize the size and performance of the Obfuscation and Boot Load Speed code, breaking structures that make programs modest, surprisingly reducing the size of program code in many cases. For example, reducing the size of metadata and optimizing symbol tables.

Resource Protection:

Resource Protection protects managed resources by encrypted resource names so that they cannot be determined if the assembly changes. Watermark software The software watermark can be used for additional hidden identification or by marking a particular application with specific information, such as its buyer and copyright. This information can help reveal a forgery of an application and identify its owner, distribution region, OEM distributor, and serial number. A watermark is embedded in an assembly in such a way that it disappears with the application after decompiling and disassembly. Integration and Automation Obfuscator's Spice.Net provides many tools to automate the obfuscation process and to Spices.Net integrate obfuscator's engine with popular build engines, Microsoft Visual Studio, MSBuild, NAnt and with custom build process. The user can control all processes step by step.

How does Obfuscation .NET work? During obfuscation, a .NET assembly is transformed into an equivalent .NET assembly that is more difficult to understand when decompiled. Some glare agents use ILDASM to unmount the assembly and then transform the original MSIL, and then use ILASM to reassemble the result. A wide variety of different techniques are applied to the tests to make the disassembled source code more difficult to understand. Below, given the brief summary of the most effective of them.

Entity Renaming:

The most essential method of obfuscation. Entities are all objects named in the .NET assembly: namespaces, classes, methods, properties, fields, and enums. As you all know, it is a good practice to give the names meanings of the entities and thus make the code easier to read and debug. When you create a .NET assembly, the names of the entities in your source code are preserved in the assembly metadata and therefore provide clues to those who try to understand the code. During the entity renaming process, all entities are renamed to short, meaningless, or incomprehensible names, making the code very difficult to read, but still operational. Overloaded renaming also takes advantage of .NET details by giving the same names to more than one entity, as long as this is allowed by .NET overload rules. The method return type can also be overloaded at the MSIL level, making the assembly code absolutely impossible to decompile.

Declarative obfuscation

This technique allows the developer to decide what exactly should be obfuscated and supports for repeated obfuscation that is well documented directly in the source code. Obfuscation of control flow and anonymization code (US patent no. 7,937,693).

This method modifies the source code so that it becomes logically more difficult to understand, while remaining logically equivalent.

Stub Methods Intact This method replaces intact method bodies with anonymous stubs.

Removal of unused members

When this approach is used, the entire source code is evaluated to determine whether there are methods that are actually unused, and if so, those members are removed from the assembly. This approach also allows you to optimize the size of the application.

String encryption String constants and literal strings in your .NET source code appear unchanged in your compiled .NET assemblies. In the obfuscation stage, they are encrypted and the decryption routine is added to the assembly to be then called at run time to return the original string values.

ILDASM breakes (disassembler) ILDASM is the MSIL disassembler that comes with the .NET Framework SDK. The breaking technique is based on the injection of a piece of assemblyed code that causes ILDASM to fail and the inability to handle the assembly.

Difference between licenses: Single (Individual) Allows you to use the product on a single machine, or in desktop /laptop, work/home settings (you can install and use products on your desktop and laptop or at work and at home). Does not allow the use of products on a machine/build server.

Team pack

Allows the use of products on up to 5 development machines and/or 1 machine/construction server.

Enterprise Allows to use in an unlimited number of development machines and create machines / servers in a physical enterprise.

System requirements:

Windows 98, Windows Millennium, Windows XP, Windows2000

.Net Framework 1.0 or later