Implementing the Post-Quantum Survivors: A Retrospective
summary
Bouncy Castle integrated the NIST Round 3 finalists and ran funded formal reviews using an Adelaide research tool and a newer bytecode analyzer called Robusta, which flags 57 issues of which about a dozen are real. The bytecode static analysis pinpoints exact methods with timing and secret‑leak risks, leading to fixes that make affected code constant‑time; tool noise and lack of suppression remain the main usability gaps, and the approach is now expanding across the BC APIs.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:11Bouncy Castle's PQC journey
- 2:35Government PQC project
- 4:22Project timeline
- 6:31API integration challenges
- 9:17PQC standards and keys
- 11:01Initial review work
- 12:29Robusta tool development
- 15:43Robusta findings
- 18:52Timing attacks
- 21:59PQC verification future
- 23:23Q&A
related talks
53mPanel: Migrating to Post-Quantum Schemes
40mPost-Quantum
31mMachine-checking post-quantum cryptography
30mMigrating and benchmarking a banking application
30mInvestigating Post-Quantum Cryptography: building a PQC decision tree for developers
19mAgile is the new black – Why Preparing for Postquantum Crypto also Matters to You!
33mExtending or Evolving: Choosing the Path to Quantum Readiness
44mQuantum Cyber Risk: How Deep and How Wide?