[TLS] Re: Boring cryptography, and the opposite extreme

"D. J. Bernstein" <djb@cr.yp.to> Tue, 15 April 2025 09:55 UTC

Return-Path: <djb-dsn2-1406711340.7506@cr.yp.to>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 534061C27181 for <tls@mail2.ietf.org>; Tue, 15 Apr 2025 02:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.496
X-Spam-Level:
X-Spam-Status: No, score=-0.496 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1LVXXgQPMHj for <tls@mail2.ietf.org>; Tue, 15 Apr 2025 02:55:13 -0700 (PDT)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by mail2.ietf.org (Postfix) with SMTP id B82DB1C2717C for <tls@ietf.org>; Tue, 15 Apr 2025 02:55:13 -0700 (PDT)
Received: (qmail 22189 invoked by uid 1010); 15 Apr 2025 09:55:13 -0000
Received: from unknown (unknown) by unknown with QMTP; 15 Apr 2025 09:55:13 -0000
Received: (qmail 198095 invoked by uid 1000); 15 Apr 2025 09:54:59 -0000
Date: Tue, 15 Apr 2025 09:54:59 -0000
Message-ID: <20250415095459.198093.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: tls@ietf.org
Mail-Followup-To: tls@ietf.org
In-Reply-To: <20250404181527.159292.qmail@cr.yp.to>
Message-ID-Hash: B2HICSHHEH35HLWGVGHYP7N5Q7ECMY7Q
X-Message-ID-Hash: B2HICSHHEH35HLWGVGHYP7N5Q7ECMY7Q
X-MailFrom: djb-dsn2-1406711340.7506@cr.yp.to
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Boring cryptography, and the opposite extreme
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/moR7mGcUKwWfpHJD7wvXtqtAmfI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

A message has just appeared on pqc-forum claiming yet another attack
improvement against lattices---improving what are called "dual" attacks
and breaking earlier claims about those attacks not working; concretely,
reducing "the security of Kyber-512/768/1024 by approximately
3.5/11.9/12.3 bits" below Kyber's security goals in the same cost model
used in the round-3 Kyber submission.

For comparison, the round-3 Kyber security analysis had claimed that
"primal" attacks for round-3 Kyber-512 (after patches to Kyber-512 in
response to earlier security issues) were ~10 bits above the goals, and
that dual attacks were "significantly more expensive" than that.

The "significantly" slowdown wasn't quantified, so the reader is left
not even knowing how much improvement there has been. Did these 5 years
of public attack development reduce the costs of Kyber-512 dual attacks
by 20 bits? 30 bits? As for the future, how much farther will the cliff
crumble? We don't know. Continued excitement for researchers! Lattice
attacks today are far less stable than ECC attacks were two decades ago.

To be clear, I'm not opposing efforts to roll out post-quantum systems:
on the contrary, we have to _try_ to stop quantum attacks. I'm simply
saying that we shouldn't be ripping out seatbelts.

---D. J. Bernstein