AxProtector .NET provides several attributes via WupiEngineNet.dll that can be used to target the protection of specific namespaces, classes and methods. The attributes are called Protection and Licen 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
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
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
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
The AxProtector option '-a' was used in the past to place the AxEngine at a previously reserved area during encryption. This was necessary when the application did not provide enough space to accommod more
This message occurs during encryption with AxProtector, if there is not enough space in the application to accommodate the AxEngine. To fix this, you need to create your application with a larger File more
The message "Error: JVMTI SetEventCallBack cannot be used." is displayed because several wibuxpm4j files are loaded into the same process space. These files try several times to modify the JVM for AxP more
Please proceed as follows: Call the encrypted application. Please adjust your proxy information. java -Dhttp.proxyHost=proxy.company.local -Dhttp.proxyPort=8080 -jar application.jar Alternatively you more
The date is set to this value after the encryption to guarantee that several encryptions of the same application are binary identical - otherwise the modification date would be different. Alternative more
The error 1001 means "FileNotFound". It occurred since your WkFirm.wbc file has not been found. The WkFirm.wbc file is required for programming licenses and encrypting applications. You should have re more
This button allows it to open tickets for the WIBU Operating Services Team. There are two types of tickets you can open here: Emergency Tickets, which are always priority level 1 (critical). If its no more
The knowledge base contains articles which are good to know and can help every user to solve frequently asked questions, basic fails, standard cases or known issues. more
By clicking on this button you can see all tickets created by your user, as well as the status for each ticket. The status shows you, how far our support team has solved your case. You can also add ne more
The prerequisite for using the function is that the person with whom you can share the ticket is either an employee of the same company unit or of a subordinate company. We can store the hierarchical more
The current CodeMeter Runtime Kit 7.10x communicates with CodeMeter License Central via Websocket API with "Origin Check". Due to the current CVE's, the internal handling has been changed so that an O more
To import the update into your FSB (Firm Security Box), please proceed as follows: I. Create context of FSB 1. Open Webmin of the CodeMeter License Central with :10000 behind the LC-IP in the web brow more