[lamps] Re: TLS Client Certificates; a survey

John Kemp <stable.pseudonym@gmail.com> Tue, 24 March 2026 11:39 UTC

Return-Path: <stable.pseudonym@gmail.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 68386D09B10A for <spasm@mail2.ietf.org>; Tue, 24 Mar 2026 04:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.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, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 1Tfkms42dUBP for <spasm@mail2.ietf.org>; Tue, 24 Mar 2026 04:39:09 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 33F31D09B105 for <spasm@ietf.org>; Tue, 24 Mar 2026 04:39:09 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id d75a77b69052e-50912a097b0so6597601cf.1 for <spasm@ietf.org>; Tue, 24 Mar 2026 04:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1774352343; x=1774957143; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=FN8eG2NAVHZBSCrpScRnfcFBSMzWmPVHdAUiSf5XRbM=; b=fpVf/1GevDnDIfUwErUwskBcaF4a/PvGDaPj3EOitakYADJidNvF8/erSt4NgUKF+p tXywcl82VHGOsD3XFsUXvSHzAqNi9MerxjEMIxPMGaNxGuv82/9Ct3vhmZpUASBPVDt2 SWbEYn8VHMk6wEQRt0JL3Zyx8q102dWyAecVODxR4MTLXkOqjgXfnTCFupEi/s6ADfEm UQ0jYbJ0IsxvsgAfjX3aDbavjIQk1z7wiYIx6HgAAwo9jSZUiSqFMj1Qa/ds+1O/dGIU DYNxQYUBKWW9nT1wwanwcCIsM2VuXfSUo61/zVfd+5yjFeKbNX7z636/7A2ZShJTN2Ls I5NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774352343; x=1774957143; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-gg:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=FN8eG2NAVHZBSCrpScRnfcFBSMzWmPVHdAUiSf5XRbM=; b=MG30N+9F+QXUaZuJ/jx0uYdvQqIVAtxPelh09o8q/E7/0ehP3gYYMdSFMIvXvQdmxf RHN1uPNFFlEkO278ztF6umB5hCDZFrCdf4kqpPtD2Y32Gx4kiWkT2IpqjxH12hYWCPI5 7Mm74iVsnQ6pq7ENX+hPLVkcyVmtG0RmcmulYGCM39TymUwqZHEfwgmrld+k4uSucJt4 ZplkZuLdLuZkgqb/iUww58TNC/4Hae7Dk5+653I1woFVkISW/gdDmzqKalJNiiiJ/0eV Gl9NmFyv+Ozs56I9vmflAqvg3ajFLcPcDo8nmjRo0NI9/ud1Lr5rO4L1ZigFvJ/YU30f GAwQ==
X-Forwarded-Encrypted: i=1; AJvYcCVZUhw4JRdzEb/ZGGQisgAxeasys24iv15OLzqDW45km4lvJGh/PLZwfRKadbprvPqEWUFI8w==@ietf.org
X-Gm-Message-State: AOJu0YxRMwGLKr0Qmm1K62T7gnKW74OzibX3FH5c7kQ50C1JJJDveyS/ 5eUkfo5j3zesU5tpzmA2zs5yR9OE/CN4Mr7IM0twz6FO/b+rQ3xzR80t
X-Gm-Gg: ATEYQzxM/MlbXnfQxrhyJjB87y232Wk3qYPL87jwOp0m7nAQjxz3eQP4lh/WFiX+6lL MZHsHKOZtZHOX33LNicrEwIBvejeSNEtJ6p88DnCxvMFQ+Wl26OBXDaD7CPnqRCwb+fCC92fTtd ihzVgZWWa0bnrzw0uKGpjBxhuefWS8vL2/UDh2hHiYg8hnQNNgcFA23fpBD2p2Pdh2AJhAaeImC vQiya8EHDn7nUPJcLBD667tChiwRL6MPsoHkIyumi7iLShC6COoUJPa1onazu3Ie6lXYDD+jCsV +O57/8Y84loJlTqLY2iMJjIrx4mndvyI9S1iNi4mmYA+ohx+fE8iYC0dzDsQ25cInrXj9v9Ak8p mPNmL05U8GjcaElWlPbM0yaF7SdTEViJuralZ4f0j56W9/A67bfq/YKJl0EDZ/cKsrQN74JkgAA 2NIrQxuw1zS59JWR2Nk6z2p9ZKebA8n0uxnmUYrUTDkBJrCPzyKd4=
X-Received: by 2002:ac8:6f06:0:b0:50b:51a0:f749 with SMTP id d75a77b69052e-50b51a0fcf8mr137484531cf.9.1774352343118; Tue, 24 Mar 2026 04:39:03 -0700 (PDT)
Received: from smtpclient.apple ([67.246.88.47]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-50b36e803b8sm103105761cf.23.2026.03.24.04.39.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Mar 2026 04:39:01 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
From: John Kemp <stable.pseudonym@gmail.com>
In-Reply-To: <MEAPR01MB3654202C8134AC3523991A7AEE48A@MEAPR01MB3654.ausprd01.prod.outlook.com>
Date: Tue, 24 Mar 2026 07:38:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <04CDF341-5314-410A-BD87-F27757CD71D5@gmail.com>
References: <MN2PR17MB40314193002D42E6ED4F465ACD4CA@MN2PR17MB4031.namprd17.prod.outlook.com> <MEAPR01MB3654202C8134AC3523991A7AEE48A@MEAPR01MB3654.ausprd01.prod.outlook.com>
To: Peter Gutmann <pgut001=40cs.auckland.ac.nz@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3864.400.21)
Message-ID-Hash: ZZXO3GXWWV7VHFRLEEYKG6U643QYYFCH
X-Message-ID-Hash: ZZXO3GXWWV7VHFRLEEYKG6U643QYYFCH
X-MailFrom: stable.pseudonym@gmail.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/Z1ML7HPZPuYYjufc-u4Ib3HbvMA>
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 Mar 24, 2026, at 03:50, Peter Gutmann <pgut001=40cs.auckland.ac.nz@dmarc.ietf.org> wrote:
> 
> Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> writes:
> 
>> Since WebPKI CA’s will not be able to issue TLS-Client certificates, what are
>> the customers and CAs thinking of doing?
> 
> Same as they've always done, which for the vast majority of all TLS users will
> be not bother with client certs.  For the rest, typically siloed deployments
> using private-label CAs and/or ignoring eKU.
> 
> And commenting on another part of the discussion about what is PKI: Non-web
> PKI isn't really PKI as such, specifically the I part, but a ticket-clipping
> service, you need to have a ticket visible on your dashboard that's been
> clipped by one of the Approved Authorities in order to participate in the
> system.  Which may sound bad but actually isn't, it's a pretty effective
> access control mechanism, and certainly vastly more so than the web PKI.

Yes. And what is the advantage of using X.509 certificates for that ticket-clipping service, over using bearer tokens as tickets a la Kerberos->SAML->OAuth? Is binding the ticket into the encrypted session with a client secret, worth “PKI"?

Regards, -johnk

> 
> Peter.
> _______________________________________________
> Spasm mailing list -- spasm@ietf.org
> To unsubscribe send an email to spasm-leave@ietf.org