System Utilities & Cross-cutting · Trust & Integrity

M35 · Licensing & Compiler

The issuer's tool that creates and signs licences, plus hardware-binding technology.

Base (always active) Implemented

Level 1 · At a glance

The issuer's tool that creates and signs licences, plus hardware-binding technology.

Benefits: Licences that cannot be forged without the issuer's private key.

Example of use: The issuer generates a 12-month licence for modules M07 and M12 and sends it to the customer.

Key capabilities

  • Signed licence generation (issuer only)
  • Licence catalogue of 42 ids
  • Hardware fingerprint and TPM proof of possession bound to licences (version 2)
  • Owner decision engine (library)
Level 2 · Technical detail

Licensing & Compiler, base module. The issuer-side universal generator genera_licenza.exe and generate_license.py (Ed25519 licence signing, calendar-month durations, 42 licence ids), never shipped to customers. Additive dcos/m35 v1.x (tested library): Host Vector V_H from real hardware attributes (SHA-256 via the M01 kernel plus Keccak-256), an owner-decision engine with 11 explicit fail-secure states (Receive != Authorize), hardware-change handling without auto-binding, and proof of possession with a NON-EXPORTABLE TPM 2.0 key (Windows Platform Crypto Provider) or a sealed software fallback. Since 2026-11-12 the licence verification of M01 (license_manager) enforces this binding for version-2 licences (dcos/m35/license_binding.py): different hardware or a failed TPM proof makes the licence invalid, an unreadable hardware identity or a missing TPM makes it unverifiable; the customer produces the binding request with dcos licenza impronta and the issuer signs it with generate_license.py emetti --vincolo.

Prerequisites

Issuer only; the private key is kept offline.

Declared limits

The generator is never distributed; the graphical generator does not yet offer the hardware binding (command line only). Binding applies to version-2 licences; the signed dcos.exe of 2026-11-12 predates it and must be rebuilt and re-signed.

Planned (roadmap)

  • Hardware-binding option in the graphical generator (genera_licenza.exe)

Owner's note

The code of every module is fully present and the modules have been verified. Any status shown as “not verified” or “partially implemented” derives solely from test gaps in the laboratory environment (for example the physical absence of a device during the test campaign), not from software limitations. Declared simulations (decision D-24) are deliberate design choices.

Interconnections

The interconnections shown are documented functional relationships (code reuse and data flows) or derive from the architectural role; they are an editorial reconstruction.

Official texts: D-COS NEXUS V130 MASTERWORK Official Documentation and official V130 presentation (November 2026).

This module is part of the integrated ecosystem

D-COS NEXUS does not sell separate modules: every capability lives inside the ecosystem. Contact us to see how it applies to your context.