Post-quantum encryption and distributed systems

Adding post-quantum encryption and signatures to an existing application without embedding a cryptographic library, with a sidecar, an HTTP API and keys that stay with you.

Neither text names an algorithm. Both ask for cryptography that follows the state of the art and can change when it moves, which leads to post-quantum cryptography.

A contract or an archive signed today will be verified for years. Why SLH-DSA, why a classical co-signature, and what it costs.

NIST's three post-quantum standards do different jobs. What each one does, its sizes, which one to use for what, and what ANSSI adds.

The Cyber Resilience Act fully applies in December 2027. What it asks of software vendors on encryption, vulnerabilities, bills of materials and updates, and the questions to ask every supplier.

ANSSI, NIST and the European roadmap all put the inventory first. What to list, in which order, and how to turn the list into a migration plan.

What post-quantum hybridization protects, how the two secrets are combined, and what it really costs, with measurements.

Three ways to bring post-quantum cryptography into an application, what each one gives you for free, and what is left for you to build.

Encrypting new data with post-quantum cryptography leaves what is already stored exposed. How to move your RSA and ECDH archives to post-quantum.

The French and European timeline for post-quantum cryptography, what hybridization means in practice, and the three projects to start now.