To enable or disable interfaces for WibuKey, you can proceed as follows. 1. Open WibuKey Control Panel The main instrument for controlling the access to WibuBoxes is the WibuKey Control Panel Applet i meer
The description of the error WK1130 is: WK1130 no user rights to manage Name kernel driver. The security rights of the current user are not sufficient under Windows NT to start or stop, install or uni meer
In WibuKey, the License Quantity of a license is represented by the difference of the User Code of two license entries. If, for example, a license with User Code 5 is to be available ten times, a lice meer
In this case, please check the following: a) Is the WibuBox 'locally' recognized on the server in the WibuKey tool of the control panel? b) Has the service 'WibuKey Network Server' actually been start meer
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 meer
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 meer
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 meer
To encrypt Java applications compiled with Java 9 or newer, at least AxProtector version 10.10 is required. If an older AxProtector Java version is used in conjunction with Java 9, an error (incompati meer
On encrypting Spring applications Wibu-Systems recommends to customize the following AxProtector options: Creating of valid Java class files To ensure that Spring on start is properly interpreting you meer
This error message usually occurs, if the AxProtector components were packed into the JAR archive when building the application or the JAR archive. Even if, for example, you use Wupi functions and hav meer
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 meer
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 meer
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 meer
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 meer
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 meer
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 meer
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 meer
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 meer
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 meer