Post-Quantum Cryptography for Software Protection and Licensing
Post-quantum cryptography (PQC) is changing how software publishers and device manufacturers plan for long-term security. A sufficiently capable quantum computer could undermine public-key methods used to authenticate software and licenses. Preparing for that possibility means more than replacing an algorithm: it means protecting license issuance, delivery, and use while existing products continue to operate.
Why quantum computing matters to software licensing
A software license is valuable only if an application can trust who issued it and whether its contents have been altered. Public-key cryptography helps establish that trust. A sufficiently capable quantum computer could eventually break widely used methods such as RSA and elliptic curve cryptography. Depending on how a licensing system uses them, that could eventually enable forged authorizations that appear valid to a vulnerable verifier. Feature control and the business models built on it would then be at risk.
The date at which such a computer might exist is unknown. The migration, however, has begun: NIST finalized standards for post-quantum key establishment and digital signatures in 2024, and EU Member States issued a coordinated transition roadmap in 2025. Neither development means every manufacturer faces the same deadline. Both make it sensible to identify long-lived dependencies now.
PQC migration is a system-wide challenge
A licensing system depends on a chain of trust. Keys and licenses are generated, sent to their destination, stored in a license container, and checked by the protected application. Connections to license management services and business systems may add further authentication points. Replacing an algorithm in one component leaves the rest of that chain, and its upgrade path, to be addressed.
The installed base makes the work more demanding. Software and devices may remain in service for many years; some security controllers cannot acquire new algorithms through an update. New post-quantum methods also change the size and format of keys, signatures, and related data. Storage, computing capacity, response times, and secure update mechanisms all matter, particularly in embedded and offline environments. A bespoke fix for one application cannot settle those system-wide dependencies.
Building a workable transition strategy
The first step is an inventory: where do public-key methods protect software, authenticate updates, or support license creation, delivery, and validation? Manufacturers then need to map deployed applications, container types, service versions, and the systems that issue licenses. This shows where an update is possible and where old and new components will have to coexist.
The next design principle is crypto agility: the ability to replace cryptographic methods as standards and security research evolve. A transition may use established and post-quantum methods together, but the combination must be engineered and tested for the particular use case. Authentication and update paths must also avoid a downgrade to weaker behavior. These are decisions for a product and its licensing infrastructure over its full service life, rather than a one-time substitution of code.
How Wibu-Systems is preparing the CodeMeter ecosystem
Wibu-Systems is pursuing a staged migration across the components involved in creating, distributing, storing, and using licenses. That scope includes hardware-based CmDongles, software-based CmActLicenses, cloud-based CmCloudContainers, and license management infrastructure where it is deployed. CodeMeter License Central is one optional layer in that infrastructure; the need to plan for PQC also applies to vendors using core CodeMeter components without it.
CodeMeter’s migration path progressively extends post-quantum protection across the licensing chain. The following diagrams illustrate this progression in a configuration using CodeMeter License Central.
Current Status – Existing architecture
In the starting configuration, license context files (WibuCmRaC) and license update files (WibuCmRaU) travel between CodeMeter License Central and the existing CmDongle generation through CodeMeter Runtime. The exchange uses conventional elliptic curve cryptography and AES-128.
First migration stage – Intermediate protection for license exchange
The intermediate stage adds an outer layer of protection using ML-KEM-1024, ML-DSA-87, and AES-256 between CodeMeter License Central and CodeMeter Runtime. The existing CmDongle generation continues to use the existing file formats and cryptography. This improves protection on one part of the exchange while retaining the existing dongle.
Final migration stage – Target architecture with a new CmDongle generation
The target system extends hybrid protection from CodeMeter License Central through CodeMeter Runtime to a new CmDongle generation that embeds an Infineon TEGRIONTM SLM22 security controller. TEGRION is Infineon’s family of hardware security controllers for protecting sensitive data and cryptographic operations. SLM22, a PQC hardware security controller certified to Common Criteria EAL6+, supports ML-KEM for establishing shared cryptographic keys and ML-DSA for digital signatures. These post-quantum mechanisms underpin the target architecture for future CmDongles. Reaching this stage requires the corresponding changes in the license management infrastructure, runtime, and dongle.
For manufacturers, the distinction matters: upgrading the runtime, protecting license exchange, and introducing a PQC-capable license container are separate parts of the transition. Specific migration steps and product availability will depend on future releases and the components in use.