Podcast
Root Causes 265: A Banner Year for Post-quantum Cryptography
Hosted by
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.
TCTim CallanIt’s a guest episode. We love our guest episodes. We are very lucky to have Bruno Couillard. Bruno is the CEO and CTO at Crypto4A. How are you doing today, Bruno?
TCTim CallanThank you so much for joining us. This is one of our year-end lookback episodes. For those regular listeners, you know every year we will be go back and we will look back at the big events that happened this year and this was definitely so far in human history the biggest year for post-quantum cryptography and so we couldn’t do year-end lookbacks without talking about post-quantum cryptography. We are very happy to have Bruno here because that’s something of an area of expertise for you and so that’s something that we want to make sure that we talk about today.
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.
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.
TCTim CallanIt was originally expected at the end of 2021. And we were all expecting it in Quarter 4 and it was the beginning of Quarter 3 of 2023.
TCTim CallanOne of the things that we’ve talked about of course in previous episodes was that it is a good toolkit but there are a lot of eggs in lattice basket. And so one of the things we’ve seen of course is that NIST is proceeding with its Round 4, which has a few purposes but one of those purposes is to diversify our approach to cryptography a little bit because I think there’s a fear – and tell me if you don’t agree with this, Bruno or Jason – but I think there’s a fear that somewhere some genius at a whiteboard is figuring out a whole new way to think about lattice-based encryption and if that happens we don’t want to be left with nothing.
TCTim CallanAnd not just dashed but just destroyed. Like they were both just roundly and completely defeated to the point where you just had to throw the strategy out.
TCTim CallanThat seems like lattice has been pretty reasonably pounded on. It’s not a completely new strategy. So that’s good. Generally, there’s a sense that the more scrutiny these things have undergone the less likely that an ah-ha moment has gone undiscovered. Which is intuitively that would make sense, right and, that doesn’t mean there isn’t an ah-ha moment that has gone undiscovered. I know there’s a lot of negatives there but it still could be that ah-ha moment would occur and we just plain haven’t discovered it yet. And for that matter, that could happen for RSA. Even though it seems very unlikely.
TCTim CallanOne of my favorite quotes. I love that quote. Absolutely. Yes.
TCTim CallanAnd so this brings us directly into the NIST Round 4. So, tell us about NIST Round 4.
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.
TCTim CallanThat’s just what I was gonna ask you. Like what are your thoughts? Like how long does Round 4 go on? How is Round 4 resolved? And do we just keep having rounds forever? Is this just the new normal?
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.
TCTim CallanIt’s interesting. You are bringing up a very good point which is cryptography in one way is one of these kind old, like you said, monolithic things. RSA was invented in the 1970s and everybody just kind of said, well, this is how it’s done. It’s just sort of foundational and it’s always there and I am reminded of Y2K. Where all of these decisions had been made – again, back in the 50s, 60s, 70s – and nobody could imagine a time when years didn’t start with 19 and then suddenly it came, and everything had to change. And it was this huge effort to go sort of rip out the ossified and put in the agile. So, this is a similar thing here. As we are ripping out the ossified, what you are saying is make sure we put in the agile. Don’t put in different flavor of ossified because if we do that then we are back to the same problem fundamentally.
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.
TCTim CallanI agree with you and we’ve talked about how I think in a lot of ways the next step is standards. So standards bodies now that they have these primitives have to go in and go at a much deeper level of saying ok, we are gonna from a perspective, we’re gonna explain to you how it is that you have to implement this so that it is interoperable, secure, future proofed, backward compatible, etc. And all of those things definitely are gonna have to go on now. The other thing that’s interesting I think and, Bruno, I know that you understand this well is there’s been a lot of direction from the U.S. Government on this topic.
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.
TCTim CallanThis is one of the things that we’ve been trying our small way to emphasize is don’t just sit around and wait for it to be handed to you. Get knowledgeable. And part of that is hybrid certs. So another interesting announcement this year was that ISARA put its hybrid certificate patent – or technology - I’m not sure what word I want to use – process into the public domain. So, tell us about that.
TCTim CallanThey’re guaranteed not to be.
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.
TCTim CallanAnd otherwise, it just is so much harder. Like, you imagine trying to accomplish this without hybrid certificates and it’s just a nightmare.
TCTim CallanOr a new thing that we don’t use today that is a result of Contest 4 or Contest 5 or Contest 6.
TCTim CallanSo that’s an interesting perspective. Don’t just think of hybrid certificates as a transitional thing for PQC. They may also just be part of our future in a more crypto-agile world?
TCTim CallanIt’s crazy. And if anyone is gonna do it, it’s gonna be Cloudflare. They have such a giant network that they control. So, there’s footprint. There’s technical resources. It’s a very technically adept company and it’s an extremely agile company and then when you put all those things together that would be the people who came out with something like this. But, still, like wow. You want to talk about being very early to the party to have Cloudflare implementing these things the same year as the standards are actually finalized is just super fast.
TCTim CallanThat’s possible as well.
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?
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?
TCTim CallanApril 13, you are fine. April 15, you are too late.
TCTim CallanThat’s cool. Like, Jason and I have been talking about this a lot for years haven’t we, Jason? And, um, it’s just been such an eventful year. Probably the last question, gentlemen, unless I missed something, is when we look back 365 days from today and we look at 2023, are we gonna say it was the most eventful year in the history of the post-quantum crypto? Is that the new trajectory we are on?
TCTim CallanYes. Yogi, what’s your opinion on that? What do you think? What do you guys think?
TCTim CallanAnd even without that, we’re gonna see all of industry spinning up. Like it’s gonna be the year of industry spins up. And that’s gonna mean lots of events, lots of change, lots of progress is gonna occur in 2023.