AxProtector CmE is the ideal solution to save time and effort when it comes to integrating protection in your embedded device software. With AxProtector CmE you can protect your software against piracy and reverse engineering in a fully automated fashion.
AxProtector encrypts the complete software package you aim to protect, and shields it with a safety shell, AxEngine. Best-of-breed anti-debugging and anti-disassembly methods are then injected into your software.
When compared with the integration of CodeMeter API, AxProtector CmE provides a high level of protection with minimal effort. For an even higher protection level, a combination of AxProtector CmE with CodeMeter API is also possible.
Supported Operating Systems
AxProtector CmE is available in the following variants:
AxProtector CmE Linux Encrypts Linux executables and shared objects for ARM platforms.
AxProtector CmE Android Encrypts Android applications for Android 4.2 and higher.
AxProtector CmE Windows Embedded Compact Encrypts executables and dynamic link libraries for Windows CE 5.0, Windows Embedded CE 6.0 and Windows Embedded Compact 7.
If you’re using Windows Embedded Standard 7, AxProtector, IxProtector and AxProtector .NET are available to you. AxProtector and IxProtector can replace AxProtector CmE in a Linux environment. These variants require CodeMeter Runtime.
Unlike AxProtector, which is based on CodeMeter Runtime, AxProtector CmE relies on CodeMeter Embedded.
The use of AxProtector CmE does not require any change to your source code. You just integrate AxProtector CmE as a post-build process. Encryption operations are carried out by AxProtector CmE after compilation of your software. AxProtector CmE is available as a command line tool and can be integrated into an automatic build system as part of continuous integration.
When you start the protected software, the code of AxEngine is executed first. AxEngine checks for available licenses. If one is detected, it is automatically allocated and used to decrypt the protected software. In addition, AxEngine runs integrity checks to verify possible tampering attacks.
AxEngine remains constantly on guard for security threats to your software using highly sophisticated anti-debugging and anti-reverse engineering methods. It immediately interrupts software execution when hazards are detected. As an ISV, you can define whether or not the license should be locked under such circumstances.
An integrated watch dog within AxEngine checks the license in the background, its integrity and possible threats at regular intervals.
Through the user message interface you have the possibility to react to events, such as the absence of a license. This allows you to show custom designed messages if your software is provided with a graphical interface. In case of headless devices, you can record these events in a log file.