[saag] Re: Attacking standardization

"D. J. Bernstein" <[email protected]> 22 Nov 2025 06:09:35 -0000
Newsgroups gmane.ietf.saag
Message-ID <[email protected]>
Nico Williams writes:
> But the
> reality is that the TLAs only really need the codepoints (which they can
> camp on) and they can use their regulatory power to get what they want.

Within NSA's 2013 quarter-billion-dollar budget to "covertly influence
and/or overtly leverage" systems to "make the systems in question
exploitable", one of the budget items was to "influence policies,
standards and specification for commercial public key technologies".
See the word "standards" there? Or look at

    https://web.archive.org/web/20250827175413/https://media.defense.gov/2025/May/30/2003728741/-1/-1/0/CSA_CNSA_2.0_ALGORITHMS.PDF

saying "hybrid solutions may be allowed or required due to protocol
standards".

BSI is managing to require that post-quantum cryptography be rolled out
only as part of double encryption or double signatures on top of
approved "classical methods" (because post-quantum cryptosystems are
"comparatively new or have been less investigated, especially with
regard to implementation security"). Meanwhile an IETF WG with "improve
security" in its charter isn't managing to do that. The money flow here
isn't exactly a secret.

---D. J. Bernstein

P.S. For readers bumping into this message who haven't seen the context:
Please see https://blog.cr.yp.to/20251004-weakened.html to understand
what's actually going on here.


===== NOTICES =====

This document may not be modified, and derivative works of it may not be
created, and it may not be published except as an Internet-Draft. (That
sentence is the official language from IETF's "Legend Instructions" for
the situation that "the Contributor does not wish to allow modifications
nor to allow publication as an RFC". I'm fine with redistribution of
copies of this document; the issue is with modification.)

_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]