Should you want to increase the security of your application by determining for yourself which parts of
your software are encrypted and decrypted and when this takes place. Then here again, you are able to
bank on AxProtector security, because WUPI and AxProtector can be used simultaneously.
WUPI is available for many programming languages and platforms. WUPI contains easy function calls
encapsulated in a dll. While implementing WUPI you work with IDs for single modules, i.e. you do not have yet
to define FIRM CODE and PRODUCT CODE, not even the copy protection system. Subsequently, AxProtector replaces
the WUPI dll in the compiled application by a static implementation, and the IDs are translated into FIRM CODE
and PRODUCT CODE. Optionally, an ID is able to simultaneously support CodeMeter and CodeMeterAct.
Figure 15: Supplementary definition of license details with AxProtector
This procedure bears many advantages:
Security for a static library
Subsequent selection of the copy protection system, i.e. subsequent switching between CodeMeter and
CodeMeterAct without recompiling
Separation of license details and implementation eases implementation
Always updated mechanisms (and thus actual security) by re-encryption with AxProtector.
31 | 44