Since WPF/Xaml/Prism applications work a lot with reflection, it cannot be easily guaranteed that the obfuscated names of methods, fields, etc. will be entered everywhere instead of the original names more
If you want to sign your assembly, you must do so after the encryption. AxProtector .Net offers the possibility to specify the keys for the signing as parameters and to sign the assembly created durin more
This performance loss is a known issue. It occurs because your original code is "moved" to a secure place, and AxProtector code is placed at the original address when encrypting your assembly with AxP more
To be able to mark certain functions for IxProtector, the function must be exported during compilation. Only then can IxProtector find the function in the binary. For marking the macro WUPIDECLFUNC fr more
AxProtectorLin can be called for the evaluation Universal Firm Code 6000010 as follows - for further options see the AxProtector help): AxProtectorLin -x -kcm -f6000010 -p13 -cf0 -d:6.20 -fw:3.00 -sl more
Please proceed as follows: 1. Export the created AxProtector project. You will receive a *.wbc file. 2. Edit the file, i.e. add functions or DLLs to be excluded, e.g. [WIBU-SYSTEMS Control File] Guid= more
Please proceed as follows: 1. Remove all WibuBoxes 2. Open the WibuKey Tool in the Control Panel and switch to "Installation“ 3. Open the Control Panel and uninstall the WibuKey driver. 4. Open [%syst more
This error may have several reasons: 1. AxProtector Runtime is missing (AxProtector version < 11.10). AxProtector Python, in order to run correctly, also needs the AxProtector Runtime package on Linux more
Problem When installing the German Development Kit (SetupDE.exe) this error message displays, if in the Regional Options the location is not set to "Deutsch (Deutschland)", but to "Deutsch (Österreich more
There exist a couple of setup options you are able to customize. As a result you then have a setup tailored to your requirements. The files you customized can be used anytime for new versions of WibuK more
When using AxProtector .NET elements can be specifically excluded from obfuscation by using attributes. For this purpose, the obfuscation attribute from the System.Reflection namespace can be used. Th more
Since AxProtector version 10.70, there is a new runtime library cprsrt.dll for .NET, which must be available at runtime. This library is secured with certificates to enable encrypted communication and more
FIPS is an optional security feature in Windows that restricts the use of some .NET Framework classes. The idea is that only specially selected crypthographic implementations should be used. More info more
Problem Your firm license file wkfirm.wbc or wkfirm.dat has been overwritten. Solution Copy your firm license file (youir own License file) wkfirm.wbc into the directory [..\WIBUKEY\Devkit\bin]. WkFir more
There is the possibility to run the WibuKey installer on Windows in a silent mode and with customized settings. To do so, please follow this short instruction: - Unpack the WibuKey Runtime Kit you wan more
In AxProtector .NET v10.70, the new runtime library "CodeMeter Protection Suite Runtime Library (CPSRT)" has been added. This is required when executing the protected assembly with .NET Framework and more
The cause could be that you are using the Java archive file openejb-javaagent.jar, which is located in the libs directory of TomEE. This Java archive file in turn loads the instrument.dll library of t more
AxProtector offers various options for debugging protected applications. AxProtector Option -cce To examine a dump file of an encrypted application/dll compared to the original code, you should use th more
Problem: Using an encrypted "fat binary", i.e. an application that contains 32-bit and 64-bit components, can cause problems on macOS. Solution: The application should be split for use/encryption to c more