Podcast
Root Causes 265: A Banner Year for Post-quantum Cryptography


Hosted by
Tim Callan
Chief Compliance Officer
Jason Soroko
Fellow
Original broadcast date
December 28, 2022
2022 was post-quantum cryptography's biggest year so far. Our hosts are joined by guest Bruno Couillard, CEO and CTO of Crypto4A. We go over many developments in PQC, including the announcement of the NIST round 3 winners, the defeat of several late candidate algorithms, isogeny-based cryptography, hybrid certificates, and the significance of April 14, 2030.
Podcast Transcript
Lightly edited for flow and brevity.
So, yes. Gentlemen, it was a big year for crytpo, for post-quantum crypto. I’m not even sure where we want to start. I actually know for sure where we need to start. The biggest part of it by far was on July 5 when NIST announced its winners for its Round 3 contest. So, tell us about that.
And so, NIST is actually canvassing the cryptographic community to figure out how to go about Round 4. How to design the next wave of algorithms so that they can compliment what has already been selected in July but I wouldn’t be surprised if we end up with a Round 5 and 6 and on and on.
And if you guys recall, in the early days of the internet – mid-90s/late-90s – there was this big, big issue with cryptography with a whole that was export crypto, there were kyper chip, that was the example where designers of protocol, designers of APIs had to be careful not to allow for, it was anti-crypto-agility if you wish. This concept remains to this day. We basically have very much a one algorithm that does a job and it’s only one algorithm. We don’t have many protocols that would say, that have this crypto-agility mindset because it was against the kind of rules that created the internet in the first place. What post-quantum is causing the world to adopt and rethink is this idea that, maybe we need to have crypto-agility at all layers – at the cryptographic engines, at the APIs, at the protocol.
And once you adopt this mantra, switching and modifying and migrating to new algorithms may become less of a pain in today’s world where we are going from kind of a monolith construct to having to adopt and adapt ourselves and our protocols to this new era. I do think once we get there and we’ve built up the tools and we have refactored our cryptographic stacks to deal with the multiplicity of capabilities, I do think we may end up with less of pushback to constantly allowing for new changes and new updates because cryptography continues to evolve but the tools we are gonna use in the future to break the crypto will be quantum tools, quantum computing tools. We will learn to use those quantum computers probably doing things we have not yet imagined and I suspect quantum computers of the future will have much more grit to break our crypto that we are thinking of today. So I suspect we will be having a bit of a churn there.
Another one that we have fixed or we’ve given ourselves more longevity is from IPv4 to IPv6. We’ve expanded the space so big that I don’t think we are gonna run out of IPv6 addresses anytime soon. I think we are gonna end up more or less building our cryptography 2.0 stack because we’ve lived under 1.0 until now but I think now we are in the process now of having to deal with the fact that we need to revisit all of these decisions of the past. But I do think when we get to cross that chasm we will likely end up with a very flexible, much more agile and built to remain agile sort of construct. Is what I do believe. Because we tend to have that approach, as we come across these big barriers to progress. Usually when we do put together the next generation, we tend to ensure that this barrier is not gonna be on our roadmap anytime soon in the future.
And then on 18th of November, there was another memo. This one from the Executive Office of Management and Budget, that absolutely took me by surprise in that the info in there was again going and taking what had already been stated, but this one had a slightly increased level, if you wish, of urgency. In that memo, they were suggesting that departments could and should start working with prototype products even if they are not standard, go test them out, go deploy them in your operational environment to figure out how they are gonna behave in the real world. That was the first time that they were opening the door to doing work with non-standard products and technology and it looked to me as, wow, things need to be done soon here. Someone somewhere wants to get things done. Fast. So, I do think there was certainly a plethora of very strong indicators – at least from my perspective – from the U.S. White House and NIST and NSA that this a real and a serious issue and we have to get going.
So the idea and the beauty of the concept of hybrid certificates is that for those machines that have not yet transitioned, they can be sent an x.509 certificate which looks and feels like a normal x.509 certificate. It has an outer body. It has a signature. All seems ok. But one difference is that it has very bulgy extensions at its core and those extensions are non-critical and the idea here is that every pieces of your post-quantum signature, your public key to validate that signature or the public key of the subscriber and the algorithms are created as extensions, x.509 v3 extensions, that are part of your x.509 general purpose certificate.
So, if I receive this and I don’t have a clue as to what these extensions mean, given that they are not critical, I simply skip over and move on. So as far as I am concerned, if I’m the client receiving this hybrid certificate, if I’m not equipped to read and use this post-quantum material, I’ll just simply ignore it for the time being. But if I have now been updated, at some future date I get my firmware update or my software gets updated and I’m now able and capable to read these extensions, I now have the ability to verify my certificate both on its classic signature, which is the outer shell, as well as validating the post-quantum signature that’s now inside this shell. So hybrid certificates have this ability to allow for a smooth transition in a world where, as you said, Tim, it would be a miracle to attempt and I’ve never, ever, ever, seen it.
So, Bruno, I can’t let you leave without asking you to reiterate something that you told Jason and me – not on this podcast but just separately – you told us about I guess an announcement that came out earlier this year from the Cloud Security Alliance. Why don’t you tell us about that?

