
2025-12-02
In this episode, Sven Rajala, International PKI Man of Mystery, is joined by David Hook, VP of Software Engineering for Bouncy Castle, to explore a surprisingly elegant change coming to X.509 certificates: the concept of unsigned certificates.
David explains that for self-signed (root) certificates, the signature itself does not add value; it does not prove key provenance, since it is signed by the same key it certifies. With post-quantum cryptography introducing much larger signature sizes, this redundancy can become costly in both storage and processing.
The new standard introduces a “no signature” option: a defined empty signature field representing a trusted anchor without unnecessary data. The result is smaller certificates, more straightforward validation logic, and a more efficient foundation for future cryptographic systems.
Bouncy Castle already supports the draft specification, with full alignment to the finalized object identifier coming in the next release. The draft is expected to be formally published as a new RFC titled “Unsigned Trust Anchors” in January 2026, which will also act as an update to the existing RFC 5280 (Internet X.509 Public Key Infrastructure Certificate and CRL Profile).

