CodeMeter License Tracking

Starting with Version 4.50 CodeMeter® introduces license tracking allowing for the evaluation of licensing data based on structured logfiles. With it the actual use of licenses is recorded.

However, Wibu-Systems does not offer a separate application for license tracking but suggests that software vendors who want to evaluate how their licenses are used refer to tools by third parties able to aggregate information from real-time requests or logfiles.

Secure Licence Tracking

Starting with Version 5.20 CodeMeter® supports Secure License Tracking. This ensures that license access log data is written manipulation-safe. Manipulation is prevented by authenticated check of data integrity using signatures.

For analyzing license access data not a single log file is created but separate logfiles for each Firm Code. Integrity and authenticity of the log files preventing tampering is ensured by signatures and a subsequent signature check.

Validation

In order to validate either the contents of a given signed CodeMeter log file or a sequence of log files located in a given directory use the option /vslf in CmBoxPgm the developer tool for local programming of CmContainer using a commandline (console).

Command

/vslf - Validation Of Signed Log Files

 

Validates either the contents of a given signed CodeMeter log file or a sequence of log files located in a given directory.

Expects the path to the file that contains the public keys to use for validation and the path to the log file respectively log directory as arguments.

Syntax

/vslf:<public key file>,<log file>|<log directory>

The <public key file> musst be created as comma separated file (CSV).

information_grau_klein26

For this file the following notation is valid:

<major version>,<minor version>, <firm code>, Ox<public key>

You can specify several different values and public keys for separate runtime versions.

You obtain the required values from one of the created CodeMeter log files.

beispiel_en

From the CodeMeter log file:

2014-06-24T06:06:19 SignedLogfile FirmCode:10, PublicKey:a809304778d517c44a22d65e1fcedd51a4e2a956fa89e93bb1a24e2100000000a2ad17e685306d6e15eb6b7ebc8cc72ebc97c0f52721b584836696de00000000, Runtime-Version:5.20.1432.500, LogfileId:1

the following <public key file> is derived:

5,20,10,0xa809304778d517c44a22d65e1fcedd51a4e2a956fa89e93bb1a24e2100000000a2ad17e685306d6e15eb6b7ebc8cc72ebc97c0f52721b584836696de00000000

Currently, the logfile content is saved locally but for future version its is planned that contents may also be retrieved using HTTP access and calls (real-time history).

information_weiss_klein26

If the logfiles need to be read from other systems, you must share the folder where the logfiles are stored as read-only in your local area network.

The following sections briefly:

show how to configure License Tracking

introduce definitons and value ranges used in the logfile

describe single logfile entry types