Crypto obfuscator 2012

Crypto obfuscator 2012

After obfuscation the code is reliably protected from analyses that can be performed by crypto obfuscator 2012 man or by a machine. Obfuscator is recommended for the cases when software protection against reverse engineering is crucial.

For example for software that contains DRM keys or other sensitive data that can’t be lost or modified. If it happens it causes financial and reputation losses. The program removes comments, spaces, joining all lines, replaces symbols, numeric constants and characters in strings with something more difficult for understanding but it doesn’t change the logic of obfuscated program. It means that binary codes for both a not obfuscated text and an obfuscated text will look the same. Developers may use this type of obfuscation when they have to supply the source code according to the license agreement.

In this case, extra branching, loops, function calls, etc. Binary codes for a not obfuscated text and an obfuscated text will be very different. Each obfuscation gives a new version of the binary file. For example, in order to stop working existing cheats and bots in the game, it’s enough to re-obfuscate the source code without changing anything inside. This option provides the highest level of protection from analysis and modification. Obfuscator belongs to the second type.

It uses different algorithms to change the program logic. Obfuscator’s benefits is its versatility as it can be applied to protect programs designed for any operating systems and any processors, including protection of firmware. The future of obfuscation prepares negative perspective for hackers. From practical point it means that it makes no sense to work with standard analytical methods.

In theory it is possible to remove trash and superfluity that were added by an obfuscator but in practice it’s very difficult. And it is almost impossible to unravel code of a Petri net because it is a one-way process and nobody is able to reverse it. The high level of protection is provided by obfuscation both the source code and the binary code. The obfuscator supports more than 30 obfuscation methods.

Most all of the methods can be enabled, disabled and adjusted independently, with the help of the configuration file. The support of all popular operation systems: Windows, macOS, Linux, iOS, Android. Obfuscator is a stand-alone application that is installed at the customer’s site. An option to set different obfuscation rules for different parts of code. To create a cheat it is necessary to analyze the game code and how it works. The more cheats are in use the less revenue the game publisher has. It even can cause the closing of the project.

Obfuscator prevents from security attacks such as tampering and malicious reverse engineering. The developer himself determines the level of protection for different parts of the code, not to reduce the performance of the game. As a result of obfuscation, each time a new version of the binary code is obtained, which makes it impossible to use the old cheats. There are many reasons to protect source code: unique algorithms, piracy threat, a part of the code hiding, etc.

In case of failure it causes financial and reputational losses. Obfuscator allows to hide the logic of your software operation. All your secrets will be securely saved. Standard DRM systems such as AACS and HDCP are used all over the world to control access to audio and video streams. A device key leak leads to pirate content distribution and as a result the discredited key is revoked by the DRM.

After that the device stops working and a producer needs to get a new key and pays a lot of money for it. After obfuscation the code that is working with DRM keys is reliably protected against analysis and reverse engineering. The front end of any DRM system, for example OMA DRM, is vulnerable to the attacks that include reverse engineering, modification and protection disabling. Depending on the DRM, an attack can result in compromising either a certain protected object or all of the protected objects of the user, or all of the protected objects in the system. Obfuscator allows reducing the risk of DRM cracking due to significant increase of the reverse engineering complexity. The development of custom DRM is a costly task. If the developer decides to do it, he should in any case solve the problem of securing the DRM code that works on the end user side, from reverse engineering.