zur Hauptnavigation springen zum Inhaltsbereich springen

채용
 
Menu

Hatching Ideas: Mastering Encryption and Obfuscation with Next-Generation Software Protection

Share:

Almost 10 years ago, Wibu-Systems faced the challenge of improving the self-protection of CodeMeter Runtime. Our own solution, AxProtector, set the standard. AxProtector encrypts the application after compilation. Depending on the selected settings, either the entire application is decrypted at runtime, or defined, critical code blocks are decrypted only when needed. However, an application protected by AxProtector always requires a license for execution, as the keys for decryption are stored within the license.

On the one hand, CodeMeter Runtime provides the licenses, which would create a chicken-and-egg problem. On the other hand, while the approach of dynamic decryption is sufficient in many cases, we wanted to elevate the protection to a new level, even in cases where no license is required.

Our intensive search for an external solution ultimately led to the conclusion that no ready-made solution existed. This marked the starting point for us to develop our own solution for the obfuscation of native (C/C++ and Rust) code. This solution intervenes during the compilation of the application: Compile Time Protection = CTP. With a plugin in the compiler, the code is modified so that later, at runtime, it becomes nearly impossible to analyze.

After this solution was developed, improved, and successfully implemented in CodeMeter Runtime and AxProtector over several years, the time came when customers began asking for a similar solution. This was the birth of AxProtector CTP. Like a dragon, it hatched from the well-guarded egg and has since protected your software against potential hackers.

AxProtector CTP not only offers obfuscation of the application but also includes all the functions provided by the classic AxProtector. The obfuscation of the entire application can be tied to the presence of a license by encrypting data and control flow. Individual functions can be protected with other licenses. The relocation of executable code to a CmDongle or a CmCloudContainer (namely CodeMoving) is supported, as well as operation without a license on the user’s end.

Access the Recordings
German access
English access

During this masterclass, we will focus on the following highlights of AxProtector CTP:

  • General technologies
  • Protection of the entire application
  • Modular protection
  • Protection without a license
  • CodeMoving
  • Advanced obfuscation options
  • CodeMeter Protection Suite Runtime (CPSRT)
  • System requirements
  • Comparison with classic AxProtector

AxProtector CTP uses the CodeMeter Protection Suite Runtime for runtime functions. This provides you with a unified interface for handling situations like "No license found" or "License expired."

Join the webinar and learn in which scenarios you should use AxProtector CTP and when the classic AxProtector is recommended instead. Maximize the protection of your applications against license violations and reverse engineering.

To top