[TLS] Re: Fwd: New Version Notification for draft-usama-tls-risks-of-mlkem-01.txt

Ilari Liusvaara <ilariliusvaara@welho.com> Mon, 01 June 2026 18:05 UTC

Return-Path: <ilariliusvaara@welho.com>
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 C4988F8CF2C9 for <tls@mail2.ietf.org>; Mon, 1 Jun 2026 11:05:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780337143; bh=0DJYyOHijU2mpA01Yf1pnNJqdal7orLBSJtLPLgFV/g=; h=Date:From:To:Subject:References:In-Reply-To; b=RDvoiU8GeS0tMBxDQENfm9PvOXyvsvuhXeP/r1MwrzBMeWDRHtN/ELE6/IcLs1JbN Zk6g0TC7NLHcXCmbkzRCs+b96BqsJSQV6+h11hKJp4aYTkUTYqVJA7kQ+jssEkbdW4 XqiI9qeS+zw+YnN70fUollEsGijpsg3owlsGVvt4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=welho.com
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 Ano4WVouel-N for <tls@mail2.ietf.org>; Mon, 1 Jun 2026 11:05:43 -0700 (PDT)
Received: from smtp.dnamail.fi (sender103.dnamail.fi [83.102.40.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 54286F8CF262 for <tls@ietf.org>; Mon, 1 Jun 2026 11:05:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.dnamail.fi (Postfix) with ESMTP id E1B2A4099FC6 for <tls@ietf.org>; Mon, 1 Jun 2026 21:05:05 +0300 (EEST)
X-Virus-Scanned: X-Virus-Scanned: amavis at smtp.dnamail.fi
Received: from smtp.dnamail.fi ([83.102.40.157]) by localhost (dmail-psmtp02.s.dnaip.fi [127.0.0.1]) (amavis, port 10024) with ESMTP id vJeGroJ7VkVY for <tls@ietf.org>; Mon, 1 Jun 2026 21:05:05 +0300 (EEST)
Received: from LK-Perkele-VII2 (87-92-117-27.bb.dnainternet.fi [87.92.117.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: hliusvaa@dnamail.internal) by smtp.dnamail.fi (Postfix) with ESMTPSA id 554C64098F3C for <tls@ietf.org>; Mon, 1 Jun 2026 21:05:05 +0300 (EEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.dnamail.fi 554C64098F3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=welho.com; s=2025-03; t=1780337105; bh=GIMIrIZXHvGLMs+mIHk44W+YYvg4u/mLGeVXddtd8gQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=rJ1wOH5pjvjId9SRBbFN7MZ1ikg7skEcZ2sG9ibSvG8ec1aF0hZYJlepq+hW1aWle RBi7lFvkqXqV9l3moI70L1GD0K2q6TnvQPsib1ykNU31wQ7NHs/ALLE/w2Mc73gPuG Ymw1AUZ/qQv5Ztu0cvW04R3+F7iYGKnqMFv23/VqhOXokyZ5pyuQjUYHna/vYoSFkc DgNwMgPUH6W0tnFfLNzM0YNYInlh9SiWpGJUgiEmQgmso+TybAzjO0GSLJiiGoLu8S +IHiOe11RsnhyzRnU0bCb0gwT9i6rvjKHkehmD98vJEy+Di7vZZDIR/20DcJiw3Klm knU3YnuM/m8gw==
Date: Mon, 01 Jun 2026 21:05:04 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: "TLS@ietf.org" <tls@ietf.org>
Message-ID: <ah3J0G3qvnHe0TCv@LK-Perkele-VII2.locald>
References: <178004897406.1571084.15428249207754239073@dt-datatracker-5b4c8598b5-4ztf9> <b9a8212d-cfe0-402b-9a8a-f63c1712d1db@tu-dresden.de> <AS4PR07MB8825B2ED5C1F97F575CF643289162@AS4PR07MB8825.eurprd07.prod.outlook.com> <d296d34a-0bb6-4a4d-aa42-3186c1f7457c@tu-dresden.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <d296d34a-0bb6-4a4d-aa42-3186c1f7457c@tu-dresden.de>
Sender: ilariliusvaara@welho.com
Message-ID-Hash: B5Z4URNPNINPSB7R7IPR25JPGWQSGWEZ
X-Message-ID-Hash: B5Z4URNPNINPSB7R7IPR25JPGWQSGWEZ
X-MailFrom: ilariliusvaara@welho.com
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: Fwd: New Version Notification for draft-usama-tls-risks-of-mlkem-01.txt
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/u53HNEQNmABfzri9vfNEcZWdmsk>
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>

On Fri, May 29, 2026 at 10:53:57PM +0200, Muhammad Usama Sardar wrote:
> Thanks all for the comments. Some thoughts inline:
> > - This concerns KEMs in general and is independent of
> > draft-ietf-tls-mlkem, ML-KEM, and PQ. [...]
> > 
> > I don’t think a formal FATT process should be started. I want
> > X25519MLKEM758 published as soon as possible.
> > 
> > 
> > Can you explain why the synmmetric argument in your draft does not hold
> > for hybrid key exchange?
> > 
> FWIW, I tried to address the concern on hybrid/X25519MLKEM758 already in
> Sec. 4.1 [0].
>
> I would like to clarify that I am not at all proposing to
> block X25519MLKEM758. Please let me know exactly where there is this
> ambiguity in Sec. 4.1. Happy to rephrase it or clarify it.

That does not address the concerns. The same issue _does_ appply to
X25519MLKEM768 — as I and some others have already explained. The
arguments about "some level of symmetry" are unsound.

Moreover, I do not think it is possible to prove soundness of
X25519MLKEM768 without proving soundness of stand-alone ML-KEM — as
soundness of X25519MLKEM768 includes it having hybrid property, meaning
it is still secure if ML-KEM is secure, no matter how throughly X25519
is destroyed.

Conversely, if stand-alone ML-KEM is not sound, then X25519MLKEM768 is
not sound either.




-Ilari