Version 8.9 got new .NET Licenser API version.
Skater .NET Obfuscator Free has been updated with new 2.1.05 version of Licenser API. It refined with latest .NET Framework and .NET Core.
.NET Licenser Web server has been remodeled with Rustemsoft cloud licensing webservice.
With .NET Licenser API you just order the protection library (.NET dll) and the .NET Licenser Web server comes free.
Version 8.8 prevents deobfuscators.
Obfuscator has been recently refined to prevent deobfuscators. Skater can NOT easily be hacked and deobfuscated by the cotemporary open source deobfuscators. That deciphering hacker's tools definitely do NOT work in renaming class/method/property/field names with the Skater .NET Obfuscator. Strings values are NOT unraveled as well.
Version 8.7 protects .NET Core assemblies.
Skater .NET Obfuscator Free Light Edition is a variant of the reputable Skater .NET Obfuscator, a code-protection tool for .NET app obfuscation. The Light version is the Free edition of Skater .NET Obfuscator. The protection tool has been developed to assist you protect .NET apps when sending them to your customers both commercial and personal usages. Skater .NET Obfuscator executes all popular software protection innovations and obfuscation techniques. If you would like systematically protect your .NET software apps the Skater .NET Obfuscator is a right tool for you. Rustemsoft is running the Skater for internal needs to achieve external goals securing all Rustemsoft commercial .NET exes and dlls.
Skater .NET Obfuscator was originally developed as a need for Rustemsoft struggling to efficiently get our .NET applications through the software source code protecting process in a reasonable time.
We checked lots of code securing software tools. We needed an application that was easy, simple and covered all areas of the .NET apps protection process. In the end we built Skater .NET Obfuscator that works in a way that makes sense to our customers.
Main features of software protection algorithm may be defined as identification of pirate's hacking to decompile or unauthorized access to software code. Skater .NET obfuscator runs the code protection by various means mostly focus on producing the assembly internal names inane, encrypting string values, and including bamboozling code commands. The .NET Obfuscator's command-line edition using in MS-DOS command-prompt batch mode is much useful for your scheduled software products modifications. You should assign obfuscation settings for your assembly in Skater interface first. Then the command-prompt obfuscation run will use the pre-stored settings. .NET Obfuscator is efficient and easy to use .NET code protection tool that secures your .NET application from competitors, hackers, and prying eyes by protecting against unauthorized use, reverse engineering, and code tampering. This is a .NET software Licensing and Protection tool. Skater obfuscates and protects your .NET software, optimizes your .NET assembly for better deployment, minimize distribution size, increase performance and add licensing features. Skater freeware obfuscator efficiently enables you to deliver a smart version of your .NET assembly, in no time and with unmatched ease.
Main features of Skater .NET Obfuscator
- [ ] Protects .NET Core DLL and .NET Standard assemblies
- [ ] Prohibits reverse engineering
- [ ] Obfuscated application usually is not recompilable
- [ ] Processes any .NET application, executable or assembly
- [ ] Encrypts string constants
- [ ] Compatible with any .NET framework from 1.0 through 4.6
- [ ] Control flow obfuscation stops decompilers and deobfuscators
- [ ] Scrambles class names, method names, field names etc.
- [ ] Protects XAML (baml) files in WPF application
- [ ] It works well on both (x86 and x64) platforms
- [ ] Provides .NET Licensing features
- [ ] Implements .NET Code Extension for small .NET applications protection.
- [ ] Implements assemblies linkage; linker unites .NET assemblies into a single dll or exe
Cardinal obfuscation techniques:
Private and Public members names obfuscation.
It scrambles names of classes, methods, variables, and other assembly members. It makes assembly code reverse engineering much harder by obfuscating names. Some Skater settings allow to generated names that will prevent recompilation.
Public members in dll libraries are advisedly reserved from obfuscation because they are intended to be used in external assembly code. If you are sure some of public members are not to be accessed from outside, you may want to obfuscate them.
For exe executables you may consider the assemblies to be self-contained, and set obfuscation of all possible names very aggressively, including Public Members.
The string encryption function allows you to select literal values of string data type to be encrypted. You may select all strings to be encrypted. Also you may mark some specific strings to obfuscate. You have choice to apply a cryptography method for the string encryption. Only specified strings will be encrypted /obfuscated.
Since Strings can provide useful clues for anyone trying to reverse-engineer your code it makes sense to protect your string data from spying eyes. It will not prevent an absolute hacker from deciphering the conversion and seeing your data. However, for example, an attacker trying to break a licensing routine would first focus attention on Strings having to do with licensing to locate the appropriate spot of code. Skater can make this more difficult by encrypting the strings in your .NET assembly. This is done by inserting a decryption routine into the assembly and calling the decryption code at runtime to return the original Strings.
Control Flow obfuscation intended to stop decompilers and deobfuscators from functioning correctly.
Control Flow obfuscation subdues reverse engineering by scrambling .NET methods (functions and procedures) code. The Control Flow obfuscation algorithm distorts and reorders the IL code in the assembly, inserting bait branch instructions while preserving code semantics. This obfuscating essentially converts assembly method implementations into "spaghetti code", making interpretation by human hackers and decompiler tools much more difficult.
Actually Control Flow obfuscation involves the insertion of additional instructions. Applying of this feature increases the size of the output assembly. If a maximum level of code protection is not required for your assembly, you may want to consider disabling this feature to minimize your output executable code size.
Control Flow obfuscation discourages reverse engineering and malicious tampering of software codes by applying false conditional statements and other misleading constructs in order to confuse and break decompilers. Given the original source codes and desired obfuscation criteria, the proposed Control Flow obfuscation works by decomposing the source codes into fragments and then applying various transforms to the code fragments. As the Skaters output, the transformed fragments are re-assembled and obfuscated with the designated obfuscation criteria. Moreover, since only Control Flows are obfuscated with a sequence of transformations that produce equivalent results of the original fragments, the final output can still preserve the same execution results as the original codes.