| Home | Installation | Licensing | Hotline | FAQ | Imprint | | Deutsch | English |

Installation on Linux

1. Step: Selecting the correct installer package

Depending on your Linux distribution you need different installation packages. For SuSE Linux 9.x, SuSE Linux 10.x, RedHat Linux 9 and Fedora you need rpm packages, for Debian 3.1 (Sarge), Ubuntu 6.06 and Ubuntu 6.10 you need deb packages.

For each package type exist different packages that need to be installed depending to the applications or requirements of your application:

CodeMeter Runtime Package
The CodeMeter Runtime Package contains all necessary files and programs for the enduser, e.g. the CodeMeter Runtime Server, the CodeMeter User Interface, the dynamic libraries and USB hotplug support.
CodeMeter Add-On Packages
CodeMeter Add-On Packages provide the so called bindings. Bindings enable e.g. to use CodeMeter also with 64bit applications (EM64T) or gcc4-compiled applications. Any Add-On Package requires an installed CodeMeter Runtime Package. Note that the CM Password Manager requires the gcc4 Add-On since this application was compiled with gcc4.
AxProtector Runtime Package
The AxProtector Runtime Package supports encrypted Java applications, that are encrypted by the AxProtector.
In most cases the installation of CodeMeter Runtime Package is sufficient.


Insert the CodeMeter CD-ROM into your CD drive. Change to the directory "Linux". Depending on the distribution move to the "deb" or "rpm" folder.

From Internet

Please download the current version the packages for your system.

2. Step: Installation of the Runtime Environment

To install the CodeMeter package please use the package-manager of your distribution. Um das CodeMeter Paket zu installieren, verwenden Sie bitte den Paket-Manager Ihrer Linux Distribution. Alternatively you can install the CodeMeter Runtime Package using the following commands:

Install CodeMeter Runtime Package by:

Uninstall CodeMeter Runtime Package by:

3. Step: First Plug In of a CmStick

Plug in your CmStick into a free USB port on your PC. The CmStick will lighten red and green for some seconds. Now you will find your CmStick as new device e.g. on your desktop.

Remark: Also CmSticks without memory are shown as an additional device, although you can not store any data on it! All data that are dragged on such a drive are lost when the CM-Sick is plugged out.

4. Step: Start of CodeMeter Runtime Server

In the menu of your window manager you now find in on of your menus depending on the window manager (Gnome/KDE) and the used distribution a new entry "CodeMeter". For Gnome it may be found in "Applications/Accessoires" and for KDE e.g. in "Utilities". Select this menu option and the CodeMeter User Interface is opened. This establishs the connection between the user and the CodeMeter Runtime Server (CodeMeterLin). If the CodeMeter Runtime Server is currently not running it is started automatically. On the CodeMeter User Interface you can start and stop the CodeMeter Runtime Server and also start the WebAdmin for configuration and detailed informations.

CodeMeter User Interface

Remark: The next two steps can be omitted if you received your CmStick directly from a software vendor. In this case the CmStick Password was set by the software vendor. Ask your software vendor for the CmStick Password. Maybe you will find it in the installation manual. Mostly the CmStick Password is set to "CodeMeter".

5. Step: Displaying the CmStick Master-Password

INow a dialog is opened automatically. It shows the CmStick Master-Password, which enables you to reset the CmStick Password in case of loss.

Attention: Please write down the CmStick Master-Password and place it in a safe place. Please note that the CmStick Master-Password is only shown once!

CmStick Master-Password

6. Step: Setting the CmStick Password

Now the dialog for setting the CmStick Password is opened. Please set a new password for this CmStick. Please enter the password twice for validation.

CmStick Password

Please ensure that you remember your new CmStick Password in the future. You can change the CmStick Password if you want, but you need to know the current one or the Master-Password.

After the Installation


^The configuration of CodeMeter is stored in the file Server.ini at /etc/wibu/CodeMeter. The configuration only can be changed if the CodeMeter Runtime Server (CodeMeterLin) is not running. But normally all necessary and useful changes can be done using the CodeMeter User Interface or the CodeMeter WebAdmin, so editing the file itself should not be necessary.


If you want to use CodeMeter within your browser, e.g. for Online-Shopping, your browser needs to support Java (>1.4.2) and JavaScript. To test this you can use the following testpage: file://usr/share/doc/CodeMeter/AppletExample.html.

Detection Problems

CodeMeter is using the Linux USB Hotplug system to detect CmSticks. Please ensure that hotplug is working well on your system.

If your kernel is correctly configured, the command codemeter-info -L will list all available CmSticks of your computer. If it does not show your CmSticks, you probably have a problem with the used linux kernel, or one of the kernel modules could not be loaded correctly.

On newer distributions the plug-in and plug-out of a CmStick may not be recognized correctly by CodeMeter. In this case your distribution may use the newer udev mechanism. To enable the detection using udev please copy the file /usr/share/CodeMeter/52-codemeter.rules to /etc/udev/rules.d/.

If you want to use CodeMeter with self-compiled kernel please ensure to compile the modules usb-mass-storage and scsi-generic-device (as kernel module).
Example of your kernel configuration::

Congratulations! Your CmStick is now ready to use and the installation of the runtime environment is finished. Register your CmStick now on my.codemeter.com to be able to lock your CmStick in case of loss.

Installation of other software packages