Re: [openpgp] Weird OIDs in the 4880bis draft

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Fri, 17 February 2023 18:49 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEAC0C14EB1C for <openpgp@ietfa.amsl.com>; Fri, 17 Feb 2023 10:49:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b="GwYqQ4Vb"; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b="IcpyA5Mm"
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 Lo7K2HwTE5_U for <openpgp@ietfa.amsl.com>; Fri, 17 Feb 2023 10:49:50 -0800 (PST)
Received: from che.mayfirst.org (che.mayfirst.org [IPv6:2001:470:1:116::7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AD13C14F72F for <openpgp@ietf.org>; Fri, 17 Feb 2023 10:49:09 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1676659747; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=pjvhVs50Jav+N8Mza/ULXYe/f2o9XSbOU2bYor95UqM=; b=GwYqQ4VbmAVhhVkz/yObvYY0YQIOKtRI80nJVtZ9aDYW+/BR7M02Z9BcjO4SW1yWOfNdB dz94ga/XhHS/uuvDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1676659747; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=pjvhVs50Jav+N8Mza/ULXYe/f2o9XSbOU2bYor95UqM=; b=IcpyA5MmVjQAfxJFibPuxskkZqcC4ZeQ+vnfEioPkFWX1cjb1LHOSlKCShZ74M+OeMRoQ TeIMGJnwa5YG39ICoMqkAMFdVvvPH9UQWn6Kn1OOAy235UwY7RuaNi4RWaulP5rZyZHr0N9 Qag6J82duk8RHHeGkaFo88U28SSqHLW2E3PV8s3XctyMS24cL5M3yx0+hcL1+8kZsMElOr8 RCCff3BK2TRVYvutZru++lg88IUXCL7WT7O8iSVji5VwK5iF+j6GilnZZKOLKFYnivrO6l1 rNxP68RtWywFFRPrP/2/EjQwdAvjxe9DivVwp32pTFw2itxyH42iVyKfDDaA==
Received: from fifthhorseman.net (lair.fifthhorseman.net [108.58.6.98]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id A4C19F9AD; Fri, 17 Feb 2023 13:49:05 -0500 (EST)
Received: by fifthhorseman.net (Postfix, from userid 1000) id CC6C820391; Fri, 17 Feb 2023 13:41:47 -0500 (EST)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Justus Winter <justus@sequoia-pgp.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Peter Gutmann <pgut001@cs.auckland.ac.nz>, "openpgp@ietf.org" <openpgp@ietf.org>
In-Reply-To: <877cwg9n2y.fsf@europ.lan>
References: <SY4PR01MB6251BD1B19BAD5DE910A1C0EEED99@SY4PR01MB6251.ausprd01.prod.outlook.com> <5bbca9f6-9fc5-3e8b-51eb-103637a6a4b5@cs.tcd.ie> <877cwg9n2y.fsf@europ.lan>
Autocrypt: addr=dkg@fifthhorseman.net; prefer-encrypt=mutual; keydata= mDMEX+i03xYJKwYBBAHaRw8BAQdACA4xvL/xI5dHedcnkfViyq84doe8zFRid9jW7CC9XBiI0QQf FgoAgwWCX+i03wWJBZ+mAAMLCQcJEOCS6zpcoQ26RxQAAAAAAB4AIHNhbHRAbm90YXRpb25zLnNl cXVvaWEtcGdwLm9yZ/tr8E9NA10HvcAVlSxnox6z62KXCInWjZaiBIlgX6O5AxUKCAKbAQIeARYh BMKfigwB81402BaqXOCS6zpcoQ26AADZHQD/Zx9nc3N2kj13AUsKMr/7zekBtgfSIGB3hRCU74Su G44A/34Yp6IAkndewLxb1WdRSokycnaCVyrk0nb4imeAYyoPtBc8ZGtnQGZpZnRoaG9yc2VtYW4u bmV0PojRBBMWCgCDBYJf6LTfBYkFn6YAAwsJBwkQ4JLrOlyhDbpHFAAAAAAAHgAgc2FsdEBub3Rh dGlvbnMuc2VxdW9pYS1wZ3Aub3JnL0Gwxvypz2tu1IPG+yu1zPjkiZwpscsitwrVvzN3bbADFQoI ApsBAh4BFiEEwp+KDAHzXjTYFqpc4JLrOlyhDboAAPkXAP0Z29z7jW+YzLzPTQML4EQLMbkHOfU4 +s+ki81Czt0WqgD/SJ8RyrqDCtEP8+E4ZSR01ysKqh+MUAsTaJlzZjehiQ24MwRf6LTfFgkrBgEE AdpHDwEBB0DkKHOW2kmqfAK461+acQ49gc2Z6VoXMChRqobGP0ubb4kBiAQYFgoBOgWCX+i03wWJ BZ+mAAkQ4JLrOlyhDbpHFAAAAAAAHgAgc2FsdEBub3RhdGlvbnMuc2VxdW9pYS1wZ3Aub3Jnfvo+ nHoxDwaLaJD8XZuXiaqBNZtIGXIypF1udBBRoc0CmwICHgG+oAQZFgoAbwWCX+i03wkQPp1xc3He VlxHFAAAAAAAHgAgc2FsdEBub3RhdGlvbnMuc2VxdW9pYS1wZ3Aub3JnaheiqE7Pfi3Atb3GGTw+ jFcBGOaobgzEJrhEuFpXREEWIQQttUkcnfDcj0MoY88+nXFzcd5WXAAAvrsBAIJ5sBg8Udocv25N stN/zWOiYpnjjvOjVMLH4fV3pWE1AP9T6hzHz7hRnAA8d01vqoxOlQ3O6cb/kFYAjqx3oMXSBhYh BMKfigwB81402BaqXOCS6zpcoQ26AADX7gD/b83VObe14xrNP8xcltRrBZF5OE1rQSPkMNy+eWpk eCwA/1hxiS8ZxL5/elNjXiWuHXEvUGnRoVj745Vl48sZPVYMuDgEX+i03xIKKwYBBAGXVQEFAQEH QIGex1WZbH6xhUBve5mblScGYU+Y8QJOomXH+rr5tMsMAwEICYjJBBgWCgB7BYJf6LTfBYkFn6YA CRDgkus6XKENukcUAAAAAAAeACBzYWx0QG5vdGF0aW9ucy5zZXF1b2lhLXBncC5vcmcEAx9vTD3b J0SXkhvcRcCr6uIDJwic3KFKxkH1m4QW0QKbDAIeARYhBMKfigwB81402BaqXOCS6zpcoQ26AAAX mwD8CWmukxwskU82RZLMk5fm1wCgMB5z8dA50KLw3rgsCykBAKg1w/Y7XpBS3SlXEegIg1K1e6dR fRxL7Z37WZXoH8AH
Date: Fri, 17 Feb 2023 13:41:46 -0500
Message-ID: <87sff4jfrp.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/1l0oSMUeVDIXjregT4cR1X-eADE>
Subject: Re: [openpgp] Weird OIDs in the 4880bis draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2023 18:49:55 -0000

On Fri 2023-02-17 19:13:57 +0100, Justus Winter wrote:
> Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:
>
>> That said, if someone were to create a merge-request
>> in the next day or two with a suggested change, and
>> if we see a clear WG consensus for that specific change,
>> then that could just about make it into the next rev.
>
> Here you go:
>
>   https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/240
>
> The gist is:
>
>   Use x509's OIDs for Ed25519 and X25519, see RFC8410.
>
>   Also, use the opaque signature wire format for Ed25519, and opaque
>   secrets for X25519.
>
>   Keep the currently used OIDs for compatibility with v4 key material.
>   Forbid its generation in v6 material.

Thanks for writing this up, Justus.

Are you advocating for it, or are you just providing it as a point of
discussion?  Is anyone on this list advocating for it?

This proposed change includes two entries for Ed25519 in the
#ecc-oid-usage table, one of which is marked "v4 only", and the other is
not marked any way at all.  Does this mean that the newly introduced
variant is allowed/encouraged when generating v4 keys, or should it only
be used in v6 keys or later?  I imagine most implementations will
generate v4 keys by default for a while after this draft comes out.  If
they're generating a 25519-based key, will they know which forms to
choose?

Would this change be clearer if it introduced a variant name for the
deprecated form of Ed25519, to make it clear that it is distinct?

For the adjustments to the tables, does it make sense to have a
parenthetical "v4 only" and "deprecated", or should there instead be a
new column marked explicitly for this kind of deprecation?  Having a
distinct column might make it easier for an implementer to make sense of
these things.

I imagine that an implementer who doesn't know the history here could be
pretty confused about what to do, and i'd hope that anyone advocating
for these changes would try to make them as clar as possible.

    --dkg