The internet is ready for some PQC certificates
summary
ML-DSA certificate chains balloon (a full ML-DSA chain hits about 14.7 KB), but using a ML-DSA-44 leaf with existing intermediates trims that to roughly 4.5 KB, which AWS tests show causes only a 3–6% performance impact. The proposal: require TLS 1.3, issue short‑lived certs (use the 47‑day lifecycle for experiments), start PQC at the leaf and work up the chain, and plan for future roots/intermediates using SKI sign or multivariate schemes to keep chain size manageable.
AI-written summary · about
chapters (15)
- 0:00PQC conference intro
- 1:27Why use PQC now
- 3:37PQC cert size and speed
- 8:31MLDSA 44 security
- 10:56Cert chain size comparison
- 13:25PQC adoption with leaf certs
- 15:55TLS 1.3 and cert lifecycles
- 17:00Leaf to intermediate transition
- 19:08Future of PQC schemes
- 21:39Future cert sizes
- 23:23Key takeaways
- 25:08Q&A on root vs leaf
- 28:22Browser support challenges
- 30:58Hybrid certs and crypto agility
- 32:01Closing remarks
related talks
55mMaking PQ Signatures work in the WebPKI
29mPQC Standardization at the Internet Engineering Task Force (IETF)
28mMixed Certificate Chains for the Transition to Post Quantum Authentication in PKI
29mWhy the Internet isn’t ready for Post-Quantum Certificates
13mNavigating the Quantum Readiness Journey: Open-Source Cryptography, PKI and Signing Tools
36mPost-Quantum Cryptography for Digital Signing
24mUpdate on end-to-end PKI and HSM integrations with ML-DSA
28mQuantum-safe PKI for the German administration