Skip to content
SECURITY · POST-QUANTUM CRYPTOGRAPHY

Post-quantum certificate tests do not all check the same thing

A new checker highlights the difference between using a public key and verifying a certificate’s signature. Proposed warnings would separately flag formatting problems.

Published Source report Sources checked
Reading tools for text size, copying, printing and your reading list
My reading list
An aisle between rows of black server cabinets with illuminated indicators in The National Archives’ server room.
Illustrative photoThe National Archives (UK)

A digital certificate is a signed record connecting identifying information to a public key. Software can read and use that key without checking the signature on the record.[8]

That distinction is visible in the IETF Hackathon’s post-quantum certificate tests. Post-quantum means cryptographic methods designed to resist attacks from future quantum computers, using ordinary computers. The project merged a new JavaScript checker on November 14. Its contributor, Amon Koike, reported 720 of 722 comparison rows agreeing with other checkers’ majority.[1][2][10]

A November 15 follow-up, still unmerged, expands the comparison to 752 rows: 748 agree, two differ and two are tied. These compare reported test outcomes; the majority is not proof of correctness.[3]

The two continuing disagreements involve certificates holding keys used to establish shared secrets. Separately, the project’s OpenSSL-based test illustrates why identically labelled rows can cover different checks.[3][5]

For these certificates, that test reads the record and uses its public key to create a secret and a message from which the matching private-key holder can recover it. It does not verify the certificate’s signature in that step. The new checker does, against the signing key required by this test set. Neither operation alone is a complete check of a website’s identity.[4][5][6][8][9]

Separate work addresses certificate formatting and other profile requirements. A draft proposal opened November 15 would add warning icons linked to detailed findings, outside the existing checker totals. It remains unmerged and does not resolve the signature-check difference.[7]

For developers, the practical lesson is to read each passing result alongside its test definition. These are contributor-reported checks of sample files, not evidence of a failure in deployed browsers.[2][3][5]

Keep your reading trail

READ NEXT

Continue exploring

All Security stories
  1. More on post-quantum security

    The web’s quantum-security upgrade has a size problem

    New funding for Let’s Encrypt supports a different way to prove a website’s identity without carrying a bulky certificate chain through every connection.

    Published · Source report · Sources checked · About 4 min read
  2. Explore cryptography migration

    Quantum-safe encryption still has an ordinary-computer problem

    A newly started European project will test how post-quantum cryptography behaves in real devices. The mathematics is only one part of keeping a secret.

    Published · Source report · Sources checked · About 4 min read