IETF Logo Mail Archive

Re: [Secdispatch] draft-leggett-spkac: Signed Public Key and Challenge

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 09 November 2022 17:23 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7BCC1522DD for <secdispatch@ietfa.amsl.com>; Wed, 9 Nov 2022 09:23:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pGJymHoP-dJv for <secdispatch@ietfa.amsl.com>; Wed, 9 Nov 2022 09:23:32 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 669B2C1522B0 for <secdispatch@ietf.org>; Wed, 9 Nov 2022 09:23:32 -0800 (PST)
Received: from dyas.sandelman.ca (unknown [IPv6:2001:67c:370:1998:c16e:e75a:a600:3913]) by relay.sandelman.ca (Postfix) with ESMTPS id 716E81F4AF; Wed, 9 Nov 2022 17:23:29 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 92028A0EFD; Wed, 9 Nov 2022 17:23:28 +0000 (GMT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 8EA4CA01CD; Wed, 9 Nov 2022 17:23:28 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Graham Leggett <minfrin@sharp.fm>, secdispatch@ietf.org
In-reply-to: <FC5C3A5D-27A2-4E87-9148-282A7CB8E192@sharp.fm>
References: <77101A6A-7D9C-4817-B16D-70505FA10C6D@sharp.fm> <CADNypP8VhSkWX-gjLAs5mTV2YzUc0LRHsNNPdeqE7DiTHjR=3g@mail.gmail.com> <171941.1667844726@dyas> <FC5C3A5D-27A2-4E87-9148-282A7CB8E192@sharp.fm>
Comments: In-reply-to Graham Leggett <minfrin@sharp.fm> message dated "Wed, 09 Nov 2022 16:05:12 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 09 Nov 2022 17:23:28 +0000
Message-ID: <417704.1668014608@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/kkK1mxZlTg347yZITLyr_DkLO-E>
Subject: Re: [Secdispatch] draft-leggett-spkac: Signed Public Key and Challenge
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2022 17:23:37 -0000

Graham Leggett <minfrin@sharp.fm> wrote:
    > I care because I wrote this:
    > https://redwax.eu/rs/docs/latest/mod/mod_spkac.html, which is an
    > implementation of the server side of keygen. I also care because it
    > made distributing certs hard that had private keys generated by the end
    > user of the certificate. The vast majority of certificate distribution

I also care, because I'm involved in cacert.org, and there is an uptick in
client-side certificate use, but... now impossible to generate new keys in
the browser :-)

    > these days is done by “here is your cert, also here is your key that we
    > generated for you and is therefore by definition not private, and
    > therefore we can’t trust anything you signed with this”.

I also hate that :-)

    > I would like to revive the standard in HTML5, but that is a moot point
    > until the (very valid) SPKAC-has-no-definition problem is addressed.

Cool.



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email