CodeMeterAct
CodeMeterAct provides you with a purely software based license management system for digital Content.
CodeMeterAct is full compatible to our classical dongle technology CodeMeter. The applications, protection tools and interfaces you are already using with CodeMeter, are also available for the copy protection system CodeMeterAct.
Unified License Manager
CodeMeter and CodeMeterAct are based on the same principles and map the same license models. The management of licenses at the customers is provided by a unified license manager (CodeMeter License Server). You simply access the interface of CodeMeter License Server, and the management of license files and dongles is automatically done for you.
A license consists of a Firm Code and a Product Code. Strictly speaking, a license may hold additional options, such as, license quantity or expiration date. The Firm Code represents a number Wibu-Systems assigns to you. Now you are able to create licenses with the assigned Firm Code. You are free to select any Product Code or further options, and thus map different modules or different products. A license file or a dongle may simultaneously hold several Product Codes.
The Firm Code with CodeMeterAct differs from the one used for CodeMeter. In case you use both protection systems, you receive two different Firm Codes. Due to the different Firm Codes CodeMeter License Server automatically knows whether to search for the license in an activated license file or in a dongle.
CodeMeterAct Binding Schemes
Licenses in a CodeMeterAct license file are bound to a PC. Specific properties of the PC or the installed OS are used to build up information used as a “Host-ID.” This Host-ID becomes part of the activation code. The activated license can only be used on the PC if the Host-ID has not changed significantly since its activation date.
CodeMeterAct’s Host-ID scheme makes use of both Hardware Binding Schemes (real hardware properties) and Configuration Binding Schemes (configurable system properties).
Hardware Binding Schemes
Four basic hardware properties are available; which can be combined, without restriction, to create the Hardware Binding Scheme:
| Hardware Property | Description |
|---|---|
| Network-Adapter (N) | Information on the network card (MAC Address), virtual adapters are not considered |
| Disk (D) | Information found on the hard disk (real serial number) |
| CPU (C) | Information found on the main processor (processor type) |
| Bios (B) | Information found in the PC BIOS |
By altering the combination of properties and by changing how many properties need to remain unchanged, the developer can control how restrictive to make this binding scheme. More restrictive schemes increase security, but also increase the number of support calls from customers who might have simply changed a hard drive (for example). The less restrictive, the fewer support calls, but security becomes weaker. For example, a scheme combining all four properties, where only one element is allowed to change, is possible. As long as three elements remain unchanged, an activated license remains valid.
The following table shows some recommended schemes:
| Scheme | Description | Use |
|---|---|---|
| N:1 | Binding to a network adapter. | Big enterprises, SMEs (Small and Medium-sized Enterprises) |
| DCBN:4 | Binding to network adapter, CPU, hard disk and BIOS. Zero tolerance towards hardware changes. | Small Office / Home Office, Games |
| DCBN:3 | Binding to a network adapter, CPU, hard disk and BIOS. Three properties have to remain unchanged, one is allowed to change. | Big enterprises, SMEs, Small Office / Home Office |
| DCN:3 | Binding to BIOS, CPU and hard disk. Zero tolerance towards hardware changes. | Big enterprises, SMEs, Small Office / Home Office |
| DCB:2 | Binding to BIOS, CPU and hard disk. Two properties have to remain unchanged, one is allowed to change. | Big enterprises, SMEs, Small Office / Home Office |
| D:1 | Binding to hard drive | Small Office / Home Office |
Configuration Binding Schemes
Compared to hardware properties, binding to configurable properties is considerably weaker. In addition, the properties cannot be combined.
| Schema | Description | Use |
|---|---|---|
| IP-Address (IP) | The IP-Address of the PC is part of the Host-ID calculation. The IP-Address is used to which the CodeMeter License Server is linked. | This scheme offers limited security, and is designed for the use in big companies as central license server. Big enterprises |
| Machine-SID (MID) | The Machine-SID and the Domain-SID in the Windows network are part of the Host-ID calculation. | This scheme is suitable for binding to a machine in the company network. Big enterprises |
| None (Non) | The license file is not bound to a PC, and able to be activated with a fixed, pre-calculated code on any number of PC. For license-related reasons, this mode works with time-restricted licenses only. | This scheme is suitable for demo versions without online activation (specification of product serial number and activation code on the package only). The activation code is the same for all installs. After the license has expired, it cannot be used again on the same PC. Small Office / Home Office (Demos) |
| Serial (Ser) | The product serial number is part of the Host-ID calculation, i.e. the Host-ID is different for each separate user. However, the Host-ID does not change with the change of computer hardware. | This scheme is designed as a simple license protection. Additionally, the developer is able to write the name of the user into the license file; read it; display it on screen; or print it. That increases the perceived individuality of the license, and raises the mental barrier to pass on the license illegally. In this scheme, activation codes can be pre-calculated, i.e. the user gets a product serial number and an activation code, enters both, and the software runs without online activation. Big enterprises |
The binding scheme is defined independently from the software, and is subsequently editable for software already encrypted with CodeMeterAct.
The end-user receives a license information file holding information on the scheme used. This license information file may be shipped together with the software, e.g. as part of the installation, or sent separately to the end-user. This way, the developer is able to individually define the scheme for each installation.
For example, the developer can produce a CD which is the same for all customers but contains a license information file with the scheme DCBN:3. This file is sent to all medium and large customers. In the event where a large wants customer wants to renegotiate his license terms. For example, covering the company-wide use of 100 licenses excluding online activation, then he simply receives a new license information file with the license bound to the IP-Address or Product Serial Number, and a list with 100 product serial numbers and activation codes.
Activation of a CodeMeterAct License
Automatic Activation
In the case of CodeMeterAct; instead of a CodeMeter stick, a license information file is delivered. This file is comparable to an empty CodeMeter stick, and holds the information of the CodeMeterAct Binding Scheme. When automatically activated, a CodeMeterAct license (a context file) is generated from the license information file, the product serial number, and the Host-ID.
The context file generated then is sent from the end-user to the developer. For this the following options exist:
- Directly from within your software by SOAP:
- You automatically generate the context file and install the update file. You are also able to easily integrate the activation using an application automatically protected by AxProtector using an error message interface (DLL).
- Directly over a website:
- An installed CodeMeter Runtime is required, the user accesses the website, and the generation of the context file and the installation of the update file are done automatically.
- Indirectly over a website:
- The context file is generated by the user and is uploaded; afterwards the new update file is downloaded and manually installed by the user. This allows activation of a license on a PC which does not have internet access.
Activation by Telephone
The automated activation requires internet access, however, not necessarily on the PC where the license has to be activated. But there must be a way to transfer data by files between this PC and another PC with internet access. In case this requirement is not met, Wibu-Systems offers activation by telephone. In contrast to the automatic activation, the license information file is not delivered empty, but holds a large part of the necessary information. Only a secret missing part, of the cryptographic keys, is transferred on activation.
With “activation by telephone,” an installation identification number (hash) is created for the existing license information file on the user’s PC and consists of the Host-ID and the product serial number. The end user informs the developer’s help line of both this installation identification number and the product serial number over the telephone.
When using the CodeMeter License Central the developer calculates the activation code, recites it to the user, who then types it into the application activation window. The license is then activated.
If a developer wants to implement the automatic activation or activation by telephone he is provided with API functions to integrate activation into his software and into his design. For the automatically protected application you will find an implementation example in the error message DLL.
Developers are also able to automate the “activation by telephone.” Here, a voice-controlled computer or a web page is used instead of a person. In this case, the end-user types in the installation identification, and receives the result by telephone or display.
Operating systems
CodeMeterAct supports following operating systems:
- Windows 2000
- Windows XP
- Windows Vista
- Windows 7
- Windows 2000 Server
- Windows 2003 Server
- Windows 2008 Server
- Mac OS X
- Linux
