Why do they want non-hybrid KEMs and signatures, anyway? Seems like a bad idea to protect all of everything with nothing but unproven crypto.
@argv_minus_one I have an introductory chart https://blog.cr.yp.to/20260221-structure.html showing the arguments and counterarguments.
Most common argument from proponents: NSA is asking for non-hybrids, ergo support non-hybrids. This argument works for (1) companies chasing NSA money, (2) companies that take any excuse for extra options as a barrier to entry for competitors, and (3) people who think that "NSA Cybersecurity" isn't a conduit for https://www.eff.org/files/2014/04/09/20130905-guard-sigint_enabling.pdf but rather an independent pro-security agency.
Welp, I think it's safe to assume that ML-KEM is already broken and so is the IETF TLS committee. Lovely.
@rsalz DJB sees a conspiracy where one may not exist ... but has a history of seeing one where it did very much in fact exist.
I think cryptographers erring on the side of extreme caution is a net benefit (and his points about unjustified and unexplained foot-dragging and resistance on Classic McEliece adoption have been well documented)
@rsalz Dual_EC specifically is an example of NSA hijacking the standards process for nefarious purposes. Maybe that was the only one ever, and an anomaly! (But see also DES back in the 90s ...)
But it would be wise to proceed with skepticism on all future contributions from a source that proved to be a bad actor. When an actor has a documented history of bad behavior, it's both natural and wise that all their future behavior face extra scrutiny and skepticism.
More recently, the arguments against hybrids seem ... weak. See e.g., https://blog.cr.yp.to/20240102-hybrid.html and https://blog.cr.yp.to/20251004-weakened.html (which has six sequels)
DJB has always been touchy and can really get into the weeds on some conspiracy theory. really smart guy but i tend to take his rants with a heavy grain of salt.
it's been this way since early usenet days.
Everything I wrote is simple and consistent and, if you look at the context of when they were made, easy to follow. For those just jumping in.
1. As a long-time person involved with the IETF I have not seen any hidden/coercive NSA involvement.
2. I accept that the EFF budget piece is accurate.
3. The term "crazy conspiracy thinking" referred to your blog posts on this topic.
I do not argue with NSA/NIST and pointed out why they could do that in the past. I find it amusing that ISO refused to standardize NSA's Simon and Speck. Perhaps they're not as good at influence as they used to be.
@rsalz @djb @darkuncle dumb questions from the sidelines:
1: doesn’t it make sense to treat NSA preferences with a bit of suspicion given their history and mission?
2: if there is strong opposition to non-hybrid, besides djb’s, doesn’t that bear listening to? What’s the benefit here in overriding the concerns?
Very much not a crypto expert, I’m assuming there’s a lot I don’t know or understand here. Appreciate any answers.
Do you have another explanation for the inexplicable push for the IETF to specify non-hybrid ML-KEM?
I looked at the list of arguments compiled by @djb at https://blog.cr.yp.to/20260221-structure.html and I don't see any particularly compelling argument in favor of such a move. Nor can I think of one myself. Certainly nothing to justify going full speed ahead like this.