IETF Logo Mail Archive

[TLS] Re: I-D Allow using serverAuth certificates for mutual TLS (mTLS) authentication in server-to-server usages - updates rfc5280 and rfc6066

Nico Williams <nico@cryptonector.com> Fri, 20 June 2025 15:35 UTC

Return-Path: <nico@cryptonector.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 34FC2376F72C for <tls@mail2.ietf.org>; Fri, 20 Jun 2025 08:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cryptonector.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 dKedeNLXJXSK for <tls@mail2.ietf.org>; Fri, 20 Jun 2025 08:35:05 -0700 (PDT)
Received: from insect.birch.relay.mailchannels.net (insect.birch.relay.mailchannels.net [23.83.209.93]) (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 00851376F723 for <tls@ietf.org>; Fri, 20 Jun 2025 08:35:04 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 97E3B8454B; Fri, 20 Jun 2025 15:35:03 +0000 (UTC)
Received: from pdx1-sub0-mail-a237.dreamhost.com (100-122-29-29.trex-nlb.outbound.svc.cluster.local [100.122.29.29]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 302E18498E; Fri, 20 Jun 2025 15:35:03 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1750433703; a=rsa-sha256; cv=none; b=6Cp68a9CRcv0PtBH71pKligrzuFHDYCSA0nROe//ebDVl8luRH7A4NMmFqD5+qpVWI06hJ hjS9XXFa77cIVXKESM0t98Nl5WaSZ7c83UKg2MHCUcCJHS1g9S7QK+nENzn4DWcYYFY8vh dSJII+pTdGlIrtIcj3i6TdgFyScZPVVJGHeJNHVAz+sRBKapf5ySEve1P2OnDrYSTIoRMu c38q3I72z4haRsG08EjoQaFHiGpyvPjAA2nhDiPFQ/voSoVCV6Voc/Qsp0+QWJElg5P/SH 0P8FyIiiTKMiFfrCGUV/mi86NDqfgWo4/TzTNoMrHM7VYgzkvQpOoJfaxoLp4w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1750433703; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=ARPflvvwaZbqgNEGykZfIAMTZxo3y9P1jUWTnXM8C0g=; b=6Tq0UMy1gyfnBimta1m9Y0oVTq0bnKB/jTJCi32HcEaZVD2epjE1pcoZ7EascY4U+4UfF9 Rmhtx1iubUAXNjeCnzgdvp5MYCV5R0xGQsDytitS9PzJyS9UnmfQe7ZkWTEhUMnfxEE1qD ztvgfx+OZL+j+hwk7ahDiIRnuAiXOi7kckdpwRhRNc/hELCUTvqYoDt4PyObYuT7tDD7OA fRc/U1GM8aD0c0xsigFLDUm1zReH9SvTGO+H87mE7FDqArdIq9h79QvQZbDT1uhWdZxyGm zJinN44BYsVbwYQrGCe9bifu/VwNlFGYY5jIF77iuaTJxbjuB36bqYetxDi83w==
ARC-Authentication-Results: i=1; rspamd-679c59f89-9stmf; auth=pass smtp.auth=dreamhost smtp.mailfrom=nico@cryptonector.com
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Inform-Tasty: 5d56ed4244ac7996_1750433703418_1087601185
X-MC-Loop-Signature: 1750433703418:1077536582
X-MC-Ingress-Time: 1750433703418
Received: from pdx1-sub0-mail-a237.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.122.29.29 (trex/7.0.3); Fri, 20 Jun 2025 15:35:03 +0000
Received: from ubby (syn-075-081-095-064.res.spectrum.com [75.81.95.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a237.dreamhost.com (Postfix) with ESMTPSA id 4bP1kZ58T3z17; Fri, 20 Jun 2025 08:35:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1750433703; bh=ARPflvvwaZbqgNEGykZfIAMTZxo3y9P1jUWTnXM8C0g=; h=Date:From:To:Subject:Content-Type; b=XLzRDoCp0HlVQzoDUvzou2Mv9++wkVJq2BAh1KoHWcSOICde/JAxNo4GXN/TFQL7k WU5Ze/ThYpchLjwRCloD+gWE7f5RFFj+9/s8CKpbhgqVoxImaMORGfEck/+RMdF2Xv TzMMdAa+5pDc8yijB7ea8uCbGKahf/4viSRFDMXf1jfTpOPVzKKidVSK2iev67jJL1 M6nwd1qCyQufpw9e85uY0N2QT8kKWXfnQ/UU2dPBbmfPaMpg/y6OCfbWaVakkbqffx CNKyS7pZUyP6ZPBPTAO9HoignsCx5vvyaDzljnG5pv9deozv0xl9VtlPslrLy/g3k0 vfrGQC8USqCfA==
Date: Fri, 20 Jun 2025 10:34:59 -0500
From: Nico Williams <nico@cryptonector.com>
To: tls@ietf.org
Message-ID: <aFV/o+j+eZH8IPav@ubby>
References: <45jp5tle7ixk7xhc57j5extnhg772nhhguqp4arvuppjuotkdo@jq5vd74bdpbg> <CAF8qwaAj8rYkRWatDuxmBQ+TQu7Yw1GPNm-Jf+W1CT0j18nwBg@mail.gmail.com> <aFOipMpzLkQa1Aaa@chardros.imrryr.org> <ed038d80-59e3-4a22-bf1c-f14968e0441b@app.fastmail.com> <aFPBwrrRNAPsOeZJ@chardros.imrryr.org> <2cfea147-5948-4027-9be5-aefb90f07f56@app.fastmail.com> <aFTPz0I/pRtAkeu/@ubby> <aFT82b7_sDXRvB9m@chardros.imrryr.org> <aFUDTGTsfZs1rbKC@ubby> <20250620070108.GA89566@veps.esmtp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20250620070108.GA89566@veps.esmtp.org>
Message-ID-Hash: 2NX7FU533S62IG46AUJVDX72TNGHAHY7
X-Message-ID-Hash: 2NX7FU533S62IG46AUJVDX72TNGHAHY7
X-MailFrom: nico@cryptonector.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: I-D Allow using serverAuth certificates for mutual TLS (mTLS) authentication in server-to-server usages - updates rfc5280 and rfc6066
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/RQi5Jlh29eBnVC-hGM4FytsUVKk>
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, Jun 20, 2025 at 07:01:08AM +0000, ml+ietf-tls@esmtp.org wrote:
> On Fri, Jun 20, 2025, Nico Williams wrote:
> > Weird.  Let's Encrypt could tell Google to take a hike on this and
> > Google would abandon their position.  So why is LE going along?  Do they
> 
> Maybe because Google could remove Let's Encrypt from the list of CAs
> of their browser?

That would break Chrome so badly that Google wouldn't even try it.  LE
almost certainly has more leverage here than Google, at least for the
time being.

Nico
--

v2.46.0 | Report a Bug | By Email | System Status