[TLS] Re: Composite ML-DSA

Viktor Dukhovni <ietf-dane@dukhovni.org> Wed, 15 April 2026 14:21 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 D6B8CDCCBF37 for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 07:21:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776262879; bh=/lBJUmfDZhJw52q6jP8vReR9pBAl9KuZDh1v4P8zuGc=; h=Date:From:To:Subject:Reply-To:References:In-Reply-To; b=FncIIDRZNyu4tKutVXtoW0i1u/8E6xvKxtiB0yi/Jed7vzABYc6IcOyCtXYGkY0h0 o0cW4ejBuEMSl2SU8bIQZYSpO+ti1LCUbtPHOhJ5L9UbFGg596/FBLzFd7pzSZLvLO jFSyr8KfYgajJpViJnXp3VeJ5WH0vCfampv/UsuY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=dukhovni.org
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 Gtu6knsb8eOW for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 07:21:19 -0700 (PDT)
Received: from chardros.imrryr.org (chardros.imrryr.org [144.6.86.210]) (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 E63AADCCBD60 for <tls@ietf.org>; Wed, 15 Apr 2026 07:19:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dukhovni.org; i=@dukhovni.org; q=dns/txt; s=f8320d6e; t=1776262765; h=date : from : to : subject : message-id : reply-to : references : mime-version : content-type : in-reply-to : content-transfer-encoding : from; bh=/lBJUmfDZhJw52q6jP8vReR9pBAl9KuZDh1v4P8zuGc=; b=W7v1WXFN7/2pBzKIRWUUvaSd4C1cx0pfheC/dOT049cZ79YVRDtqrcAyI4ai3UAZwIFUF oP+6UtPQfaJRL0HsZ3lk90lgoH9f3d7k8oN22jdezS3C8kJxFokjXLvhdKpjB4bVAzvrB/5 RQ3m5EQFLE+BXcmDAfShMDMGFb4Uty4=
Received: by chardros.imrryr.org (Postfix, from userid 1000) id 24F55937704; Thu, 16 Apr 2026 00:19:25 +1000 (AEST)
Date: Thu, 16 Apr 2026 00:19:24 +1000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: tls@ietf.org
Message-ID: <ad-ebC8qSVHEgKcW@chardros.imrryr.org>
References: <DS4PPFA08475C7DBE27468E40C672197481C1242@DS4PPFA08475C7D.namprd11.prod.outlook.com> <LV0PR21MB6623B48B1F3A05D745F5A79D8C242@LV0PR21MB6623.namprd21.prod.outlook.com> <ad0svakv_WUM3btz@chardros.imrryr.org> <CAF8qwaBU_YHWX2MsWeeaOJ8sutR1wMozvbiTJF5kyvTE8YjWWA@mail.gmail.com> <CACsn0c=GDta824UF7uJ3nw_4U_rT=XhYOGHRemMWa+2AdbsiAg@mail.gmail.com> <3a16c7c4-345e-48ce-af70-a3bf503c8caf@app.fastmail.com> <CACf5n7_0hdeHJXXucva9pb=+pjhcgveHRpjA8XAcXB3LsYUvaw@mail.gmail.com> <CAFpG3gcC+UfO7E=ADGhwr2En5PwipZiq_r6_RdqvmT-5nnh2jw@mail.gmail.com> <d69ba150-0257-4e64-9abb-9229d03a03a6@app.fastmail.com> <87a4v42urw.fsf@josefsson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <87a4v42urw.fsf@josefsson.org>
Mail-Followup-To: <tls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: EXOK45DGHXERVLULB4EFOXRGGPOQZC2G
X-Message-ID-Hash: EXOK45DGHXERVLULB4EFOXRGGPOQZC2G
X-MailFrom: ietf-dane@dukhovni.org
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
Reply-To: tls@ietf.org
Subject: [TLS] Re: Composite ML-DSA
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/RV4Ng0Zt8KHnQMRLV3p2RDnAeUY>
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 Wed, Apr 15, 2026 at 03:54:59PM +0200, Simon Josefsson wrote:

> If your protocol allows a man-in-the-middle attack, it is REALLY bad.

This assumes significant deployment of an already broken by adversaries
non-hybrid PQC TLS signature scheme.  But nothing of the sort is
happening.

Rather, essentially ever TLS deployment (a few bleeding-edge hobbyist
systems aside) is still using classical certificates, and no mainstream
CA issues PQC certificates for TLS, and until PLANTS is complete no
realistic scale deployment.  That gives us some years before we have to
worry about whether pure ML-DSA (or a competitive replacement) is good
enough, and perhaps by that time a more clear indication of whether the
classical component is likely to provide any value.

Catastrophic failure of today's RSA or ECDSA certificates is widely and
credibly assumed to not yet be an issue.  Nobody has yet cashed in
Satoshi's coins. :-)

My personal server sporing an ML-DSA certificate as a "dogfood" (or be
it "gunfoot") exercise is not a reason to jump from the frying pan into
the fire and deploy composite certificates in TLS now.  I remain
strongly inclined to NOT implement composite certificates in TLS.

-- 
    Viktor.  đŸ‡ºđŸ‡¦ Đ¡Đ»Đ°Đ²Đ° Đ£ĐºÑ€Đ°Ñ—Đ½Ñ–!