[lamps] Re: TLS Client Certificates; a survey

Nico Williams <nico@cryptonector.com> Mon, 23 March 2026 18:10 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: spasm@mail2.ietf.org
Delivered-To: spasm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 7D4BFD0188A4; Mon, 23 Mar 2026 11:10:12 -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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 (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 A9uQAzwRa-iQ; Mon, 23 Mar 2026 11:10:12 -0700 (PDT)
Received: from serval.cherry.relay.mailchannels.net (serval.cherry.relay.mailchannels.net [23.83.223.163]) (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 3A163D0187D6; Mon, 23 Mar 2026 11:09:47 -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 121F66C3F58; Mon, 23 Mar 2026 18:09:40 +0000 (UTC)
Received: from pdx1-sub0-mail-a202.dreamhost.com (100-119-11-147.trex-nlb.outbound.svc.cluster.local [100.119.11.147]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 5DD9B6C40C8; Mon, 23 Mar 2026 18:09:38 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; d=mailchannels.net; s=arc-2022; cv=none; t=1774289379; b=1Zc7CSJ+QSkQeE6FvF60P8CnsamjIwMB4zEBmSTkdIk4jRm0Kvsv6JvXm4KnQj59Awn9F+ 5uKqQ8UXODUaj5LnC82uhlRdOky45NBy3Z1CHsKOAQGSEekdhUisVThxnM8Po8YbAqE/O4 f/K9dRI9z/fF6D7Qg+Fu6VY0QDlAynh+D3Qpn8E0rskNdUjuHyUTwdKVfzbDkJxVfcnJzE b7V2n8ByPOAvgT30lUJin2eAOo0UH8zhXxnFX30I8YxiBqS8BYObNRuV4TS+iWgcsBE7J1 wcamxEIRXZQoiCjM7qfBQMPGpNOnUpyL1ccNDuiNp1gTig3UhyJJMwxASImCkw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1774289379; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=/atV+zilhbU/pbtCl/MErfpWg3RPv+HSVEWKmoHKWGI=; b=X/Jf+1KpS2WBBUFw4AxRcQIhWtxaa8hD9K8zLddkH8K2ad0tvsP8S8YPCc2u954lw6AJ+D PVLxIpKrUrepHDi/UvWIQHx4rQUKRgt9Qi5XJm8TdGkC7Mn/BNRR4WPcOXErfpGHFM+Hzr sAUL6PLtq6B4bGJBxSC0o4Zp8kMCASdO01l/G42OmavyI0jUa2BPRgd87cpxd3vE+/8mtd u4TH6vv+OG7I5nBcTguVf+/k+ARpmDL0UI29Ct4QVaeSnNwkEvM/xmpcHp5EvuE1igdKqP qBEJ4O0XpAi2fH1wLlRhKZfWMQ1Vx/1w/Kd6JSc/xVy6yLlu2zgOI4djIVoMXA==
ARC-Authentication-Results: i=1; rspamd-6d4cb6745-kxld7; 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-Keen-Harbor: 3f1ece3f5f2bfa27_1774289379916_959029756
X-MC-Loop-Signature: 1774289379916:3907081976
X-MC-Ingress-Time: 1774289379916
Received: from pdx1-sub0-mail-a202.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.119.11.147 (trex/7.1.5); Mon, 23 Mar 2026 18:09:39 +0000
Received: from ubby (unknown [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-a202.dreamhost.com (Postfix) with ESMTPSA id 4ffh5Y4H4QzDm; Mon, 23 Mar 2026 11:09:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1774289378; bh=/atV+zilhbU/pbtCl/MErfpWg3RPv+HSVEWKmoHKWGI=; h=Date:From:To:Cc:Subject:Content-Type:Content-Transfer-Encoding; b=VGiO1eaIKwSWavd4LTPe1RFhM9hxak2uK95S9n8xOf5yfp6mVsa7Mjct5W6v+nAnp WX7tr2PmX4kUfP4zfkXyCoxYQOC4p7T7JVFr+ukGzwWqJzwDmCz/YKYSmgB46weBdb MDn79EWXXU1Snp40+i4YXNGzBHo2EKD9ryTI0u/u7P7IjE4xT9u9ew6jeqEJa7/AhQ 3Ai8lEvcfIgEsQQ/QMafahiuthFO/sjt+kU1WdEDMFK//8QKlgmmAChwj8A3zlKuJA kvdsy/xlV51RgZlE2sRy/LIZXAIH9UT+KJ9qVM8AYopbGtZoRkhjxzEOZTHxEJObRl C4o9zXgZw4sMg==
Date: Mon, 23 Mar 2026 13:09:35 -0500
From: Nico Williams <nico@cryptonector.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <acGB3/g8HMNNOP4J@ubby>
References: <MN2PR17MB40314193002D42E6ED4F465ACD4CA@MN2PR17MB4031.namprd17.prod.outlook.com> <4732.1774288835@obiwan.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4732.1774288835@obiwan.sandelman.ca>
Message-ID-Hash: WDK6ZXAHZVPUTECXFQ2KPTARNSEBQIZG
X-Message-ID-Hash: WDK6ZXAHZVPUTECXFQ2KPTARNSEBQIZG
X-MailFrom: nico@cryptonector.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Tls <tls@ietf.org>, "spasm@ietf.org" <spasm@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: TLS Client Certificates; a survey
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/lFcQuej6p3AuPBg3n2vWBS_OQjE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Owner: <mailto:spasm-owner@ietf.org>
List-Post: <mailto:spasm@ietf.org>
List-Subscribe: <mailto:spasm-join@ietf.org>
List-Unsubscribe: <mailto:spasm-leave@ietf.org>

On Mon, Mar 23, 2026 at 02:00:35PM -0400, Michael Richardson wrote:
> Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>       > Since WebPKI CA’s will not be able to issue TLS-Client certificates,
>       > what are the customers and CAs thinking of doing?
> 
> You say this as if it's a new thing :-)

well, it's recent.  It happened around October 2025.

> Is it the "change" that certificates obtained for code signing or email use
> will have the tls-kp-clientAuth EKU ommitted?

The change is that roots in the Chrome Root Program may not sign
intermediates that sign any EE certificates having any EKUs other than
id-kp-serverAuth.  A CA can still have roots outside the CRP that do
sign intermediates that do sign non-server EE certificates, but probably
few will.

>     > Replies to be will be summarized to both lists. Please be careful if
>     > you use reply-all.
> 
> 1. This assumes the RP are checking EKU.

Yes, but they should.

> 2. I think 94% of usage of mTLS is via private PKI for the client side.

Probably true.  The two applications I know to be affected are XMPP and
SMTP.

Nico
--