
From nobody Sun May  2 12:35:33 2021
Return-Path: <angel@16bits.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 218A23A1122 for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 12:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mLLLT_4b7Hmp for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 12:35:29 -0700 (PDT)
Received: from mail.direccionemail.com (mail.direccionemail.com [199.195.249.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E62093A1121 for <openpgp@ietf.org>; Sun,  2 May 2021 12:35:28 -0700 (PDT)
Message-ID: <80412ac99a5883d26ae3524ffb39d3fa1a1d1991.camel@16bits.net>
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
To: openpgp@ietf.org
Date: Sun, 02 May 2021 21:35:24 +0200
In-Reply-To: <2587c395-7ce0-c9dd-817c-1b53321a8ed@nohats.ca>
References: <20210317145508.136021-1-dkg@fifthhorseman.net> <5a927ffed96b38efa08c58b6a29e565dff87a535.camel@16bits.net> <87blbfpr9b.fsf@wheatstone.g10code.de> <9cf9ae77e21fa330918df0754707e9304a41fd36.camel@16bits.net> <2587c395-7ce0-c9dd-817c-1b53321a8ed@nohats.ca>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/xhndQ2-SBg05UrNyffKjmG8rWCc>
Subject: Re: [openpgp] The checksum may appear
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 02 May 2021 19:35:31 -0000

On 2021-04-28 at 23:58 -0400, Paul Wouters wrote:
> On Thu, 25 Mar 2021, =C1ngel wrote:
>=20
> It is not clear to me what the WG would like to do here on the
> "optional checksum" item.
>=20
> =C1ngel proposed something, Werner agreed, but then =C1ngel wasn't sure
> anymore. It would be good to get more and/or clarified views on this
> issue.
>=20
> Paul

Hello Paul

There are two points here.

I proposed a change. Its summary could be "Make explicit that the
checksum is optional".

Werner agreed. But he also mentioned "making the CRC a SHOULD create".
He might have read that into my text (it wasn't my intention on that
patch), or it could have been meant as "we should also make it a
SHOULD".

Making the checksum a SHOULD is the piece I discuss in my second mail,
and the one I'm unsure about.

I still support my initial change (well, if it doesn't turn out to be
unclear).

So there are two issues:
a) if the proposed text is good
b) whether adding a line "clients SHOULD create a checksum"


Best regards




From nobody Sun May  2 14:07:23 2021
Return-Path: <angel@16bits.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 304FD3A091C for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 14:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQKxMf2kuMWn for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 14:07:16 -0700 (PDT)
Received: from mail.direccionemail.com (mail.direccionemail.com [199.195.249.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFDFF3A091B for <openpgp@ietf.org>; Sun,  2 May 2021 14:07:16 -0700 (PDT)
Message-ID: <ac0b040d1feca39a7f820dd6f1a242ae16f6abc0.camel@16bits.net>
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
To: openpgp@ietf.org
Date: Sun, 02 May 2021 23:07:13 +0200
In-Reply-To: <87eeetaxsj.fsf@fifthhorseman.net>
References: <87wnu86mep.fsf@fifthhorseman.net> <20210324021213.333485-1-dkg@fifthhorseman.net> <87pmzp2taf.fsf@fifthhorseman.net> <26945b02701cdbcf7af0ebd3adaa325b91021be7.camel@16bits.net> <87blb72yto.fsf@fifthhorseman.net> <029c60b6a313d33cf5cc7e15791be8c0c582370c.camel@16bits.net> <ba29e6e3-7fe8-4ed6-819c-b0d0a22ec24@nohats.ca> <b4c6cb0b929dff027b28df546e4d90560dbba94f.camel@16bits.net> <dba9a771-a2b5-640-a9ba-7883b174ddd4@nohats.ca> <87eeetaxsj.fsf@fifthhorseman.net>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/VfFD9Twth9Je2kiOQZy3A1i5vHg>
Subject: Re: [openpgp] [RFC4880bis PATCH] Drop "Compatibility Profiles" section.
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 02 May 2021 21:07:21 -0000

On 2021-04-29 at 11:57 -0400, Daniel Kahn Gillmor wrote:
> > I've merged in this change in a seperate commit, please review as
> > part
> > of the next draft update. (commit 464ac8232f9)
>=20
> I think the commit you're talking about is now public as
> 1edfd5d45a49a5a15d08eff9fff7d5c482acb6da, 'update text on "Simple S2K
> and Salted S2K specifiers" as per WG discussion'.
>=20
> minor clarification: among a few other changes, it adds this line:
>=20
> +Implementations SHOULD NOT use these methods on encryption of both
> keys and messages.
>=20
>=20
> I think this "both" should be "either" -- otherwise, the guidance
> sounds
> like it applies only to some combination encryption (which isn't
> possible iirc).  otherwise, it looks good to me.
>=20
>          --dkg

Yep, it's clearly that one. It's basically my=20
https://gitlab.com/Angel-Gonzalez/rfc4880bis/-/commit/43946c9a300ebac26d788=
38ab80893685349289f
with the "SHOULD avoid" changed into "SHOULD NOT", as discussed. Paul
probably ended up in a catch-22. The "both" was originally present as
"SHOULD avoid (...) on encryption of both keys and messages". I agree
with doing the s/both/either/ in the new text.


Best regards



From nobody Sun May  2 15:20:18 2021
Return-Path: <angel@16bits.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 878823A0E62 for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 15:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Ah01TZxxhXv for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 15:20:11 -0700 (PDT)
Received: from mail.direccionemail.com (mail.direccionemail.com [199.195.249.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4B653A0E61 for <openpgp@ietf.org>; Sun,  2 May 2021 15:20:11 -0700 (PDT)
Message-ID: <48632bd5e0a602563870d4811062961f35e11956.camel@16bits.net>
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
To: openpgp@ietf.org
Date: Mon, 03 May 2021 00:20:07 +0200
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/QJigoyHG-rAnQMdOYVDGFuZgymE>
Subject: [openpgp] v5 fingerprints and public keys
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 02 May 2021 22:20:17 -0000

Some comments reviewing the recent v5 commits.

Note 0ffeeaad535232a0976a3e52ba3290df941aa47d leaked some text related
to the future AEAD string-to-key ("4 optional fields", "AEAD tag", "254
or 253"...). I'm only removing them for being unspecified in the
current document.

Best,

=C1ngel


diff --git a/crypto-refresh.md b/crypto-refresh.md
index 087f29f..c4e36a7 100644
--- a/crypto-refresh.md
+++ b/crypto-refresh.md
@@ -414,7 +414,7 @@ It may be ill-formed in its ciphertext.
=20
 A Key ID is an eight-octet scalar that identifies a key.
 Implementations SHOULD NOT assume that Key IDs are unique.
-{{enhanced-key-formats}} describes how Key IDs are formed.
+{{key-ids-and-fingerprints}} describes how Key IDs are formed.
=20
 ## Text
=20
@@ -1140,7 +1140,8 @@ MUST be present in the hashed area.
 (8-octet Key ID)
=20
 The OpenPGP Key ID of the key issuing the signature.
-If the version of that key is greater than 4, this subpacket MUST NOT be i=
ncluded in the signature.
+This subpacket MUST NOT be included in the signature if the version of tha=
t key is greater than 4.
+If the superior Issuer Fingerprint subpacket is also present, their conten=
ts MUST match (Issuer would contain the low
 64 bits of the value stored in full in the Issuer Fingerprint).
=20
 #### Key Expiration Time
=20
@@ -1480,7 +1481,7 @@ It is useful when one signature needs to refer to, or=
 be incorporated in, anothe
=20
 The OpenPGP Key fingerprint of the key issuing the signature.
 This subpacket SHOULD be included in all signatures.
-If the version of the issuing key is 4 and an Issuer subpacket is also inc=
luded in the signature, the key ID of the I
ssuer subpacket MUST match the low 64 bits of the fingerprint.
+If an Issuer subpacket is also included in the signature (only possible fo=
r keys earlier than version 5), the content
s of the Issuer subpacket MUST match those of the Issuer Fingerprint.
=20
 Note that the length N of the fingerprint for a version 4 key is 20 octets=
; for a version 5 key N is 32.
=20
@@ -1708,8 +1709,8 @@ A version 4 packet contains:
   This is algorithm-specific and described in {{algorithm-specific-parts-o=
f-keys}}.
=20
 The version 5 format is similar to the version 4 format except for the add=
ition of a count for the key material.
-This count helps parsing secret key packets (which are an extension of the=
 public key packet format) in the case of a
n unknown algoritm.
-In addition, fingerprints of version 5 keys are calculated differently fro=
m version 4 keys, as described in the secti
on "Enhanced Key Formats".
+This count helps parsing secret key packets (which are an extension of the=
 public key packet format) in the case of a
n unknown algorithm.
+In addition, fingerprints of version 5 keys are calculated differently fro=
m version 4 keys, as described in {{enhance
d-key-formats}}, "Enhanced Key Formats".
=20
 A version 5 packet contains:
=20
@@ -1738,7 +1739,7 @@ The packet contains:
   Any other value is a symmetric-key encryption algorithm identifier.
   A version 5 packet MUST NOT use the value 255.
=20
-- Only for a version 5 packet, a one-octet scalar octet count of the next =
4 optional fields.
+- Only for a version 5 packet, a one-octet scalar octet count of the next =
3 optional fields.
=20
 - \[Optional\] If string-to-key usage octet was 255 or 254, a one-octet sy=
mmetric encryption algorithm.
=20
@@ -1748,7 +1749,7 @@ The packet contains:
 - \[Optional\] If secret data is encrypted (string-to-key usage octet not =
zero), an Initial Vector (IV) of the same l
ength as the cipher's block size.
=20
 - Only for a version 5 packet, a four-octet scalar octet count for the fol=
lowing secret key material.
-  This includes the encrypted SHA-1 hash or AEAD tag if the string-to-key =
usage octet is 254 or 253.
+  This includes the encrypted SHA-1 hash if the string-to-key usage octet =
is 254.
=20
 - Plain or encrypted multiprecision integers comprising the secret key dat=
a.
   This is algorithm-specific and described in section {{algorithm-specific=
-parts-of-keys}}.


From nobody Sun May  2 19:20:14 2021
Return-Path: <paul@nohats.ca>
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 BD62B3A1B05 for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 19:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJgCWO3Bn7yK for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 19:20:08 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 102593A1B02 for <openpgp@ietf.org>; Sun,  2 May 2021 19:20:07 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4FYRWl2PXRz1bq; Mon,  3 May 2021 04:20:03 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1620008403; bh=NeNONfoJQ2i+iQvVPiWzHGsOEfVIVtnUKdNVsIN4aCE=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=g4VgM703SJJ1ILNJeR8OrvH7uLLmG5t/5ujt2IO1er7Dvz3axIfKh+VBoZ/WTz7RD ownJDhKytRdcLY9Dega3x7unwpOE4oRYiCoRZppKgTDsQ4cEwjlMVeMdibx9pfgK+q 3E7ECxF/DnOYcdikx1ErgjvNTAxq+wWIxEsL2AkE=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id nFW7RhQ5lw4G; Mon,  3 May 2021 04:20:02 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon,  3 May 2021 04:20:01 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 5892F47A34; Sun,  2 May 2021 22:20:00 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 54AC047A33; Sun,  2 May 2021 22:20:00 -0400 (EDT)
Date: Sun, 2 May 2021 22:20:00 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: =?ISO-8859-15?Q?=C1ngel?= <angel@16bits.net>
cc: openpgp@ietf.org
In-Reply-To: <0b29b5c446910e9dfe1ac89854f17012fc143851.camel@16bits.net>
Message-ID: <a5ebe3f-758c-9e13-3384-21b54561718d@nohats.ca>
References: <875z1p7vva.fsf@fifthhorseman.net> <0b29b5c446910e9dfe1ac89854f17012fc143851.camel@16bits.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/XlzOlqwFCrDE8dMbe4xpgFMZu8I>
Subject: Re: [openpgp] incomplete/confusing guidance around "Hash" Armor header for cleartext signing framework
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 03 May 2021 02:20:13 -0000

On Thu, 18 Mar 2021, Ángel wrote:

> On 2021-03-17 at 09:28 -0400, Daniel Kahn Gillmor wrote:
>> The current draft (and RFC 4880) seems internally inconsistent about
>> the
>> mandatory nature of the "Hash" armor header in the Cleartext Signing
>> Framwork section.
>>
>> In particular, it defines 'one or more "Hash" Armor Headers' as an
>> official part of what a clearsigned message looks like, but then it
>> discusses what it means when such a header is absent.
>
> And it was copied from rfc2440 as well.
>
> I think the phrase
>>      - One or more "Hash" Armor Headers,
> should have been
>>      - One or more Armor Headers,
>
>
> Then it covers other armor headers that may be present, such as
> "Charset:", and then it suddenly makes sense the following discussion
> about a missing Hash header.

I did not see (or miss?) other people agreeing or disagreeing on this
chance. Before I commit anything, I would like to know if the WG agrees.

Paul


From nobody Sun May  2 19:28:30 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: openpgp@ietf.org
Delivered-To: openpgp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE463A1B47; Sun,  2 May 2021 19:28:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: openpgp@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: openpgp@ietf.org
Message-ID: <162000890347.32435.4967470047809381389@ietfa.amsl.com>
Date: Sun, 02 May 2021 19:28:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/9HPoeHi5giVEb2PKouCk9q5h9p4>
Subject: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-03.txt
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 03 May 2021 02:28:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Open Specification for Pretty Good Privacy WG of the IETF.

        Title           : OpenPGP Message Format
        Authors         : Werner Koch
                          Paul Wouters
	Filename        : draft-ietf-openpgp-crypto-refresh-03.txt
	Pages           : 117
	Date            : 2021-05-02

Abstract:
   { Work in progress to update the OpenPGP specification from RFC4880 }

   This document specifies the message formats used in OpenPGP.  OpenPGP
   provides encryption with public-key or symmetric cryptographic
   algorithms, digital signatures, compression and key management.

   This document is maintained in order to publish all necessary
   information needed to develop interoperable applications based on the
   OpenPGP format.  It is not a step-by-step cookbook for writing an
   application.  It describes only the format and methods needed to
   read, check, generate, and write conforming packets crossing any
   network.  It does not deal with storage and implementation questions.
   It does, however, discuss implementation issues necessary to avoid
   security flaws.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-03.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-openpgp-crypto-refresh-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Sun May  2 19:33:21 2021
Return-Path: <paul@nohats.ca>
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 951613A1B72 for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 19:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uF2Yn44eKiZ for <openpgp@ietfa.amsl.com>; Sun,  2 May 2021 19:33:14 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 632693A1B74 for <openpgp@ietf.org>; Sun,  2 May 2021 19:33:14 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4FYRpv6Xv9z1bq for <openpgp@ietf.org>; Mon,  3 May 2021 04:33:11 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1620009191; bh=qr6ekPZqYWfdoJno+pmqkJkbfL9TrjxS1Qp7wTVCKb4=; h=Date:From:To:Subject:In-Reply-To:References; b=kg2koL+9IBlogtz3E1g2OVKAxPYwamruuHJaLBp6Yw2fq2Al+LoZp6k+0jJ5aHYqz BMTOIhBR5fnyuFShTDvHQ6VaPSPmyMZeI5EgoBdnGIz+/ymHWEPH2FXtGE8xfu8jwG BFdz0RUWgZPseDxVv9viuyIvi5RJHeON8mtSrfxE=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id e7vfjGSN7nrV for <openpgp@ietf.org>; Mon,  3 May 2021 04:33:10 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <openpgp@ietf.org>; Mon,  3 May 2021 04:33:10 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id EB06247A49; Sun,  2 May 2021 22:33:08 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id E38F747A48 for <openpgp@ietf.org>; Sun,  2 May 2021 22:33:08 -0400 (EDT)
Date: Sun, 2 May 2021 22:33:08 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: openpgp@ietf.org
In-Reply-To: <162000890347.32435.4967470047809381389@ietfa.amsl.com>
Message-ID: <232ea5a-11-b855-d999-478634859092@nohats.ca>
References: <162000890347.32435.4967470047809381389@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/Svy-514LXhwkIaFOyzmQtOPk7tU>
Subject: Re: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-03.txt
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 03 May 2021 02:33:20 -0000

On Sun, 2 May 2021, internet-drafts@ietf.org wrote:

> Subject: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-03.txt

> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-openpgp-crypto-refresh-03

This release fixes the items discussed on the list in response to the
-02 version. If further merges in somre more items, most notably v5 key
format, removal of old ciphers, addeding some new ciphers.


* 74b1148 - (HEAD -> main, origin/main, origin/HEAD) update my affiliation (79 seconds ago) <Paul Wouters>
* 9428808 - (tag: draft-ietf-openpgp-crypto-refresh-03) Clarify CRC is optional. Use MUST instead of SHALL (11 minutes ago) <Paul Wouters>
* ca55965 - s/both keys and messages/either keys and messages (20 minutes ago) <Paul Wouters>
* 27e70ca - use s0 s1 to denote the checksum octets instead of c0 c1 (4 days ago) <Paul Wouters>
* b705758 - Clarify CRC24_GENERATOR code with Hal Finney's second suggestion. (4 days ago) <Paul Wouters>
* 1edfd5d - update text on "Simple S2K and Salted S2K specifiers" as per WG discussion (4 days ago) <Paul Wouters>
* f310cd3 - Reference Notation flag registry (4 days ago) <Daniel Kahn Gillmor>
* f35e852 - Avoid mentioning IDEA, CAST5, Blowfish, and TripleDES in examples (4 days ago) <Daniel Kahn Gillmor>
* 71d14ac - minor textual clarifications (4 days ago) <Daniel Kahn Gillmor>
* df7dc92 - forbid S2K 255 for v5 secret keys (4 days ago) <Daniel Kahn Gillmor>
* af71082 - v5 signature format (4 days ago) <Daniel Kahn Gillmor>
* d230c7d - Issuer Fingerprint subpacket (4 days ago) <Daniel Kahn Gillmor>
* 3d3b18b - forbid the use of "Issuer" (keyid) subpacket with v5 keys (4 days ago) <Daniel Kahn Gillmor>
* 60e7a86 - introduce v5 fingerprint (4 days ago) <Daniel Kahn Gillmor>
* 0ffeeaa - Introduce the v5 key format (4 days ago) <Daniel Kahn Gillmor>
* bbcdd63 - Include EdDSA (4 days ago) <Daniel Kahn Gillmor>
* df39837 - Merge branch 'clean-up-crc24' into 'main' (4 days ago) <Paul Wouters âď¸>
* 998f554 - Clarify CRC-24 C example implementation (7 weeks ago) <Daniel Kahn Gillmor>
* 0c23c76 - Drop "Compatibility Profiles" section. (6 weeks ago) <Daniel Kahn Gillmor>
* ded0b29 - ignore more generated files (7 weeks ago) <Daniel Kahn Gillmor>
* 8c4824f - More README.md cleanup (7 weeks ago) <Daniel Kahn Gillmor>
* c9c0222 - bump version to -03 in preparation of upcoming work (7 weeks ago) <Daniel Kahn Gillmor>
* d804d4e - update README to include suggestions for release process (7 weeks ago) <Daniel Kahn Gillmor>
* edab546 - Move older drafts out of the way (7 weeks ago) <Daniel Kahn Gillmor>
* e02a925 - drop no-longer-relevant build accessories (7 weeks ago) <Daniel Kahn Gillmor>
* e6c95c0 - Document repository better in README (7 weeks ago) <Daniel Kahn Gillmor>

As always, please review and let us know on the list if there are any
issues. Meanwhile, we will prepare the -04 version for next week,
folding in the next set of changes.

full commit history available at: https://gitlab.com/openpgp-wg/rfc4880bis/

Paul


From nobody Mon May  3 08:47:03 2021
Return-Path: <masanoriogino@gmail.com>
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 928113A19A1 for <openpgp@ietfa.amsl.com>; Mon,  3 May 2021 08:47:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYW5WWjnPxQA for <openpgp@ietfa.amsl.com>; Mon,  3 May 2021 08:47:00 -0700 (PDT)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8507F3A1ADD for <openpgp@ietf.org>; Mon,  3 May 2021 08:46:36 -0700 (PDT)
Received: by mail-ej1-x62b.google.com with SMTP id zg3so8558636ejb.8 for <openpgp@ietf.org>; Mon, 03 May 2021 08:46:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=K4dw4c1l+cV2qcSNXOkUD26tHEA29iqBOAQIeAenqoU=; b=dq1VDm6PwUnLXo/NiSHlj26vcwADAl2ZX4AR1bXjm12Sxo6ExEu4KhGrXSXmA7TPtT nJx4rE/RzvnLHYtLeoxzGKl9g8T4SNHtBv5MUyJltRDpoc231oT1je2nQkngLjyPkxgn Jzzhk07pqZPEFs3GqBP7m9VXxxLxUBIPWLpkC4SPxN5DXdjkk5uOm1Fy9QiE44C3YH8B hm+uzKuHw81P6AUEIKprortED+yj9Fh8EhPxcN09cTJ3qNRO90t5oC6Df3Q3RgmgRsB6 jPmu0LroZNewFHVQS0dgP7Q4JDgY+2gNgbrjIyPxgLSWXvwUNjtFkmwgAywP9btwEm/s mJMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=K4dw4c1l+cV2qcSNXOkUD26tHEA29iqBOAQIeAenqoU=; b=d2q+gb3kbjap2UlNuMpObTnEsiGmvtCFUpSQvcIjPKhISRAAHpBVTE+cyw1zCTRntU lg2uSJGdMRzUxgG/CxH0DryQrEDthQS0TUBKfjsc3rAbTlupMUpz4XlMOMTJUGrrvdsB eray3bKi1X1SxBiv5G1J4l8SlyR3RwfT7bPhkFdev7mmZdPy1G9xx8dFffZQ1Qin1hjc KkwvP9oJNrwYs0cgO6OqL4tzF7ettX1YsCH6ax7wBQV01lWc/v3TX+QMIbLy+BwMGwgS 6SCYpyOWO3oCBviPCSyUuSUKr8pOnuw4HJ61kospWSC9VhU1lDHJ2T2LVFt4QFEwnWP2 kVMQ==
X-Gm-Message-State: AOAM5325qIw1RLOHlVNjwr5W0j1Sl88+HGR5Rid68pXi6xbGppRXr0DW Xh2oORQu0gFpw1EqGUyyOzUy8kdKchT6nq4kmxjwKhqcKoY=
X-Google-Smtp-Source: ABdhPJzrMxlswYXw2ISUb17q7snRw1tIvrVJx+3A6MvowPIpwanvkw+j0vCq4//q+ZNK0dIZbZzu32xnD82fUAvhjaI=
X-Received: by 2002:a17:907:c10:: with SMTP id ga16mr16818629ejc.402.1620056794197;  Mon, 03 May 2021 08:46:34 -0700 (PDT)
MIME-Version: 1.0
From: Masanori Ogino <masanori.ogino@gmail.com>
Date: Tue, 4 May 2021 00:46:23 +0900
Message-ID: <CAA-4+jefpHydcNfdiQ6g-adwxU9MPcb0mpAx6dQpRi_Y=W6wgw@mail.gmail.com>
To: openpgp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/cdvG1p2t3ePPizQZ0ME41WsENt8>
Subject: [openpgp] A comment on draft-ietf-openpgp-crypto-refresh-03, section 5.5.2
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 03 May 2021 15:47:02 -0000

Hello,

>From draft-ietf-openpgp-crypto-refresh-03, 5.5.2:

   There are three versions of key-material packets.  Version 3 packets
   were first generated by PGP version 2.6.  Version 4 keys first
   appeared in PGP 5 and are the preferred key version for OpenPGP.

   OpenPGP implementations MUST create keys with version 4 format.  V3
   keys are deprecated; an implementation MUST NOT generate a V3 key,
   but MAY accept it.

These sentences lack information on the V5 format whereas mentioning
that there are three versions in the beginning. It might be better to
add some words for the V5.

Best,
Masanori


From nobody Mon May  3 11:58:36 2021
Return-Path: <ilf@zeromail.org>
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 748B53A0542 for <openpgp@ietfa.amsl.com>; Mon,  3 May 2021 11:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.297
X-Spam-Level: 
X-Spam-Status: No, score=-1.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eS588qo2WbuK for <openpgp@ietfa.amsl.com>; Mon,  3 May 2021 11:58:29 -0700 (PDT)
Received: from smtpin.nadir.org (fry.nadir.org [217.114.68.218]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A05ED3A04BC for <openpgp@ietf.org>; Mon,  3 May 2021 11:58:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtpin.nadir.org (Postfix) with ESMTP id 942627D220C for <openpgp@ietf.org>; Mon,  3 May 2021 20:58:24 +0200 (CEST)
Received: from smtpin.nadir.org ([127.0.0.1]) by localhost (fry.nadir.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c1dDBVn8RI7c for <openpgp@ietf.org>; Mon,  3 May 2021 20:58:24 +0200 (CEST)
Received: from snail.zeromail.org (mail.zeromail.org [217.114.68.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpin.nadir.org (Postfix) with ESMTPS id 58DC37D21F3 for <openpgp@ietf.org>; Mon,  3 May 2021 20:58:24 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])ng TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by snail.zeromail.org (Postfix) with ESMTPSA id 11FEEBFB76 for <openpgp@ietf.org>; Mon,  3 May 2021 20:58:21 +0200 (CEST)
Date: Mon, 3 May 2021 20:58:15 +0200
From: ilf <ilf@zeromail.org>
To: openpgp@ietf.org
Message-ID: <YJBHx5fvQ3qOCSvN@zeromail.org>
Mail-Followup-To: openpgp@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/wwNIzmRlfqUcwJRxVDbLECKvS9s>
Subject: [openpgp] don't emit version armor header by default
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 03 May 2021 18:58:34 -0000

(I'm not an expert if this is the correct time for this - I hope so. :)

Currently, Section 6.2 sais:

> Currently defined Armor Header Keys are as follows:
> "Version", which states the OpenPGP implementation and version used to 
> encode the message.

https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-03.html#section-6.2-10

I propose to add this sentence:

> To minimize metadata, implementations SHOULD NOT emit this key and its 
> corresponding value except for debugging purposes with explicit user 
> consent.

We discussed this on gnupg-devel in 2016 and here in 2019. Then, dkg 
explained:

> The version of GnuPG in use is not particularly helpful.  It is not 
> cryptographically verifiable, and it doesn't distinguish between 
> significant version differences like 2.0.x and 2.1.x.

> Additionally, it leaks metadata that can be used to distinguish users 
> from one another, and can potentially be used to target specific 
> attacks if there are known behaviors that differ between major 
> versions.

> It's probably better to take the more parsimonious approach to 
> metadata production by default.

https://lists.gnupg.org/pipermail/gnupg-devel/2016-August/031424.html

See this example for a real-world attack: 
https://www.csoonline.com/article/2904395/mistakes-that-betrayed-anonymity-of-former-dea-agent-and-silk-road-investigator.html

This is rough consensus and running code in all implementations I can 
find:

GnuPG: https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=c9387e41db7520d176edd3d6613b85875bdeb32c
GPGTools: https://github.com/GPGTools/MacGPG2/commit/831c2ed77d2ce88134ad4d689414051dc99dc3b3
SKS: https://bitbucket.org/skskeyserver/sks-keyserver/commits/4af75b3526d9
LibTMCG: http://git.savannah.nongnu.org/cgit/libtmcg.git/commit/?id=2c8a6861ab839cb58b6483a04a7b584423a27811

If this gets adopted, we should probably remove it from this example: 
https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-03.html#name-example-of-an-ascii-armored

Thanks, and keep up the good work!

-- 
ilf

If you upload your address book to "the cloud", I don't want to be in it.


From nobody Fri May 21 10:25:02 2021
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 E83123A18A2 for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 10:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level: 
X-Spam-Status: No, score=-1.306 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, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=jSlEySFc; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=R4eOZu/7
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V9I1jZ6JUWzE for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 10:24:55 -0700 (PDT)
Received: from che.mayfirst.org (unknown [162.247.75.117]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CFE23A18A0 for <openpgp@ietf.org>; Fri, 21 May 2021 10:24:55 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1621617893; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=JizpHl2zx3/nUz1aLdHRZKSCDVql6BVffr+zML2BRY4=; b=jSlEySFcPrRCNvQZ+RvG00/TF+3y3kjP47cz780AjOn6IOiepkSjbb65XpwELq0inja8w spUZcsM60Atkkb5Aw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1621617893; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=JizpHl2zx3/nUz1aLdHRZKSCDVql6BVffr+zML2BRY4=; b=R4eOZu/7VTWr9pHDy4xn1e/ZwAYmh/9PuP9xWHZ/QrlcyDZt+RkHLBUtfU06P33PWWOZn 78NbzrtYjWHPFFptTkSdUfOGrKuUTRie6tCSUlbncMh/zLVnADEcC9tLpEsrs7kHfY6Lf2R 7OG7pNxwgHnCc/31sQOuvTlx/heYOgYRWe5wo6mbbU99rSXCpjhkwil3yrg69UB/SU0T5aC DhS8tFetW5aQxLUH9fTZPjse0CRGlGRbd3pcBklAXLuHv9RMRpX9eE9gDOb/lnmE291KG4K /hBRIoT2SGCDAhzFugdFoAJ55xaZA5Bqo3+46ImeUpgIVMJJk4O0Dzn1vcuQ==
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 RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 05D95F9A5 for <openpgp@ietf.org>; Fri, 21 May 2021 13:24:52 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 72CA721272; Fri, 21 May 2021 13:24:49 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: openpgp@ietf.org
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, 21 May 2021 13:24:48 -0400
Message-ID: <87bl94dmov.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/PJ8GjOH-dnZ53wB8T16DOdX9-aM>
Subject: [openpgp] OpenPGP certificate structure: multiple binding signatures on subkeys? (MR 43)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 21 May 2021 17:25:01 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi OpenPGP folks--

in https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/43 and
https://gitlab.com/openpgp-wg/rfc4880bis/-/issues/25 vanitasvitae
suggests that the structure for OpenPGP certificates (aka "Transferable
Public Keys", aka "keyblocks") is wrong.  He recommends this change:

=2D-- a/crypto-refresh.md
+++ b/crypto-refresh.md
@@ -2914,8 +2914,8 @@ The format of an OpenPGP V4 key that uses multiple pu=
blic keys is similar except
         User ID [Signature ...]
        [User ID [Signature ...] ...]
        [User Attribute [Signature ...] ...]
=2D       [[Subkey [Binding-Signature-Revocation]
=2D               Primary-Key-Binding-Signature] ...]
+       [[Subkey [Binding-Signature-Revocation ...]
+               Subkey-Binding-Signature ...] ...]
=20
 A subkey always has a single signature after it that is issued using the p=
rimary key to tie the two keys together.
 This binding signature may be in either V3 or V4 format, but SHOULD be V4.


There are two things happening here:

 - the binding signature is correctly identified as a
   Subkey-Binding-Signature, not a Primary-Key-Binding-Signature. (the
   primary-key-binding signature (the "cross-sig") is, where
   appropriate, expected to be embedded in the subkey-binding-signature
   itself)

 - there can be more than one binding sig revocation, and more than one
   subkey binding signature


This matches my understanding of how OpenPGP certificates are
structured, and I believe most implementations work this way.

I've opened
https://gitlab.com/sequoia-pgp/openpgp-interoperability-test-suite/-/issues=
/52
to request a test for this, but it may not be necessary if the WG has
consensus that this is correct.

I note that if the change in the structure is correct, then the text
below it should also be changed (it should not say "has a single
signature after it=E2=80=A6")

          --dkg

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYKfs4QAKCRA+nXFzcd5W
XCDjAP9aQL2RKlutl1MutM4EbCd/LV4i19Wo4uup/b134Vm9igEA1uxGHW581UYu
Op75Iqd3WmfcRzyQuIQamrStmA+fMw8=
=Hq14
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri May 21 10:25:06 2021
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 EA6553A18A3 for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 10:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=cY6qPqX2; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=pRBeU7Ee
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R73eyB7gQ4Z3 for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 10:24:55 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [IPv6:2001:470:1:116::7]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB9083A189E for <openpgp@ietf.org>; Fri, 21 May 2021 10:24:55 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1621617893; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=ozxUrGCs/cW1pQ1vs2cjxdb6sDjA9rcfD04hF+f+FPo=; b=cY6qPqX2+TmrGEo4zLy60r5oDpOGVNFZyeX7Wv2EHn7HnN8eFw78vT0/5hmtL/6MNsMm+ fSCY9bHuPHuhy2LAg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1621617893; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=ozxUrGCs/cW1pQ1vs2cjxdb6sDjA9rcfD04hF+f+FPo=; b=pRBeU7Ee+sFrV2aOkEaSIqSJP+E9ME9f3tNUCkQMG9b51UsRMd2h33dS0ru6RWwr8NArY 9j9FPVpIXhbTE16mVSEaI1UYp89uXqHi5GmmzjnsYFtQj/YUBcjZ54CyrGvXPvmILeYioUT 75SoiEBqJ86Biq97mF55oxfqfbQSkzK3WmDDPtnkEc54UEdQQaWtG3JFNFdjZ4M1WkXHkV5 wkIabPOhy7QAGftX629nidQ2uxSssML4MBHwOYwRmIqCpnkVGH7nV0QbDIw7ulToYVRhzAY JDQjDOQPTuzNovAgqJGTIaXnGkvidBeaGCYfT/2uBodV89m3NON2FxYTaZHA==
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 RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 0E17CF9A6; Fri, 21 May 2021 13:24:52 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id A840D2040E; Fri, 21 May 2021 12:15:44 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: ilf <ilf@zeromail.org>, openpgp@ietf.org
In-Reply-To: <YJBHx5fvQ3qOCSvN@zeromail.org>
References: <YJBHx5fvQ3qOCSvN@zeromail.org>
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, 21 May 2021 12:15:43 -0400
Message-ID: <87eee0dpw0.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/i4mLEbeoEunk0Qjqes06RlJHCzw>
Subject: Re: [openpgp] don't emit version armor header by default
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 21 May 2021 17:25:01 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon 2021-05-03 20:58:15 +0200, ilf wrote:
> This is rough consensus and running code in all implementations I can=20
> find:
>
> GnuPG: https://git.gnupg.org/cgi-bin/gitweb.cgi?p=3Dgnupg.git;a=3Dcommit;=
h=3Dc9387e41db7520d176edd3d6613b85875bdeb32c
> GPGTools: https://github.com/GPGTools/MacGPG2/commit/831c2ed77d2ce88134ad=
4d689414051dc99dc3b3
> SKS: https://bitbucket.org/skskeyserver/sks-keyserver/commits/4af75b3526d9
> LibTMCG: http://git.savannah.nongnu.org/cgit/libtmcg.git/commit/?id=3D2c8=
a6861ab839cb58b6483a04a7b584423a27811
>
> If this gets adopted, we should probably remove it from this example:=20
> https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-03.html=
#name-example-of-an-ascii-armored

Hearing no complaints or objections, i've opened this merge request
following ilf's recommended wording:

   https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/45

Regards,

   --dkg

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYKfcsAAKCRA+nXFzcd5W
XEk4AQD9oRWWKEFs6FH9DtAuud+RkQHTioGd7/3qIRq9fdPTdQEA2ZRleLVd1Qtc
bmoI89nKee5zIwZGcW0yUEfHDZDIUA8=
=ZEb+
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri May 21 10:49:08 2021
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 77CBE3A1947 for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 10:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level: 
X-Spam-Status: No, score=-1.306 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, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=7YGjypmX; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=buY9DYlq
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcSS99FHxpF3 for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 10:49:01 -0700 (PDT)
Received: from che.mayfirst.org (unknown [162.247.75.117]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B89AC3A1945 for <openpgp@ietf.org>; Fri, 21 May 2021 10:49:01 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1621619339; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=0MULJmObabGRlQCZmC3oJkvPX1OnrYsgzTaFnma/2+c=; b=7YGjypmX/sLzcgs6Sxp2WlbiDUtH/m08biCQ+7yHvwbbT6oryejiWq8w5YuUGplINawB5 c+YED4Nk0CuGi6zDg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1621619339; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=0MULJmObabGRlQCZmC3oJkvPX1OnrYsgzTaFnma/2+c=; b=buY9DYlq2HJZ2qVPBrP63qRL3HCPk8XxuaPC9XLAQReeIug39Z5zs0n5w4lEK/sTpGYRk LRbaf0d8w+xA70tDbV3k3agSfevAMC8nZDNLbwjaBdMkQNe0rHY3trmycMymi/+g3NpKRe+ F+Ix8kQP2j0kJ2/JqW8XtNH3e2CWk6l/LnnQATc2+Hjpni6E2QUlikUkbXMQglJbmqGmj/l f6Wed4CWMWNZg2Pz2KS1sVOanfkvoKgjMrwqDoD2kM1nNEO4dI6nEs5hH4/EIWbMvfSVIJH Uygg1mKGSTRMNlM1YDr1UCuaEHPHS34f61Wjd1pV0wfOTcI/q+CEgQbIc48Q==
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 RSA-PSS (4096 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id C3358F9A5 for <openpgp@ietf.org>; Fri, 21 May 2021 13:48:59 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 779C82040E; Fri, 21 May 2021 13:48:57 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: openpgp@ietf.org
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, 21 May 2021 13:48:56 -0400
Message-ID: <878s48dlkn.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/YBCZLnSdDBoa4L6JUE_cXKObVcg>
Subject: [openpgp] Ed25519 and digest choices (issue 31)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 21 May 2021 17:49:07 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Over on https://gitlab.com/openpgp-wg/rfc4880bis/-/issues/31, jethrogb
writes:

> Appendix A contains an example for EdDSA. The example states that the
> hash function used is SHA2-256. The example also states that the curve
> used is 2b06010401da470f01, which is defined as =E2=80=9CEd25519=E2=80=9D=
 elsewhere in
> the draft. However, RFC 8032 specifies Ed25519 as an instantiation of
> EdDSA with specific parameters, one of which is that H is SHA2-512 and
> PH (in the ph case) is SHA2-512. Is it the intention that OpenPGP
> implements not Ed25519 but some other form of EdDSA? If yes, this
> should be called out explicitly in the text and it shouldn't be called
> Ed25519. If no, the example needs to be updated and it would probably
> be good to explicitly call out Ed25519ph in section 14.8.

How does the WG think this should be resolved?

I intend to sign this message with an EdDSA signature from a Curve25519
key, but it will likely use SHA2-256 as the OpenPGP digest choice (in
the EdDSA RFC 8032 framing, that would be the pre-hash "PH" parameter to
EdDSA).  This would mean that we are *not* using Ed25519ph, since
OpenPGP permits variance of the PH parameter.

One approach would be to clarify that OpenPGP signatures made with
Ed25519 SHOULD use SHA2-512 as the OpenPGP digest, which I believe would
align it with Ed25519ph.  But there would still be existing signatures
out there (like the one signing this message) which would use SHA2-256,
and it's hard to say that signature verifiers should reject those
signatures.

Alternately, maybe we should instead reframe OpenPGP's use of Ed25519 as
a "PureEdDSA" scheme that signs only the OpenPGP digest (not the signed
data directly).  That bypasses the "PH" parameter, but it also means
that any cryptanalsis that is applied to EdDSA isn't necessarily
applicable to OpenPGP, because we have this additional step involved.

Either way, it seems that we need to clarify the standard.

       --dkg

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYKfyiQAKCRA+nXFzcd5W
XOsCAP9jDJ4SrynBKFF9XMvLx0t+4dxsRYPAw3JI3EtKVQpJ5wEAwTc9XHwmrs1Q
PXLs9X/YWZUNxAw99K03pzeDrGfOzAI=
=3VSz
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri May 21 11:06:39 2021
Return-Path: <paul@nohats.ca>
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 CFEA63A19E4 for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 11:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dk8az69Owd6v for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 11:06:32 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBC5C3A19E0 for <openpgp@ietf.org>; Fri, 21 May 2021 11:06:31 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4FmvgR5VjtzDRQ; Fri, 21 May 2021 20:06:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1621620387; bh=Sb3lmvR62qrZuniZUW+J0l40FW1OybYmvdOsgGPh3jo=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=UsKO7/1x/o0ktTZq9PBIyjYxOn9pdsDpEtAIPaCD2zYFb/PoJhnZkz0pSlw+TGdHp GhPbUiUXrPvWtSMwzX+j7e4aDug9B1SXJAf/NLKBeJOfOGT6KUOwd8HVc5AxHCF8uL O+Dmyi+vQYR1uMCyPoIV+zBVeOEDzbNX3QctRTCs=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id lbXfdC97YO23; Fri, 21 May 2021 20:06:26 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 21 May 2021 20:06:26 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 196B55D599; Fri, 21 May 2021 14:06:25 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 166C45D598; Fri, 21 May 2021 14:06:25 -0400 (EDT)
Date: Fri, 21 May 2021 14:06:25 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
cc: ilf <ilf@zeromail.org>, openpgp@ietf.org
In-Reply-To: <87eee0dpw0.fsf@fifthhorseman.net>
Message-ID: <534128e0-1676-b4a8-3246-5c133bf8dc79@nohats.ca>
References: <YJBHx5fvQ3qOCSvN@zeromail.org> <87eee0dpw0.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/eGJn9NJ0UbJqTGYu_jrCMFKzTSo>
Subject: Re: [openpgp] don't emit version armor header by default
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 21 May 2021 18:06:37 -0000

On Fri, 21 May 2021, Daniel Kahn Gillmor wrote:

> Hearing no complaints or objections, i've opened this merge request
> following ilf's recommended wording:
>
>   https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/45

merged.

Paul


From nobody Fri May 21 11:14:23 2021
Return-Path: <vanitasvitae@fsfe.org>
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 167C53A1A22 for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 11:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level: 
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ZfdKHhckbxZ for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 11:14:17 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2BD03A1A1F for <openpgp@ietf.org>; Fri, 21 May 2021 11:14:17 -0700 (PDT)
Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4FmvrT1WnvzDqr4; Fri, 21 May 2021 11:14:17 -0700 (PDT)
X-Riseup-User-ID: A2F5CE2FAA05DB59A4EF76C653249DD939DB20BDF087943940F0A5194FC379D0
Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews2.riseup.net (Postfix) with ESMTPSA id 4FmvrS2b6vz1xph; Fri, 21 May 2021 11:14:16 -0700 (PDT)
Date: Fri, 21 May 2021 18:14:12 +0000 (UTC)
From: Paul Schaub <vanitasvitae@fsfe.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: openpgp@ietf.org
Message-ID: <076a1bac-b6c5-4975-8c24-e5c90ffbd5be@fsfe.org>
In-Reply-To: <87bl94dmov.fsf@fifthhorseman.net>
References: <87bl94dmov.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;  protocol="application/pgp-signature";  boundary="----=_Part_10_180247185.1621620852991"
X-Correlation-ID: <076a1bac-b6c5-4975-8c24-e5c90ffbd5be@fsfe.org>
Autocrypt: addr=vanitasvitae@fsfe.org; prefer-encrypt=mutual; keydata= mQINBFfz1ucBEADXSvUjnOWSzgW5hXki1xUpGv7vacT8XqqGbO9Z32P3eFxa4E9J vveJmx+voxRWpleZ/L6XCYYmCKnagjF0fMxFD1Zxicp5tzbruC1cm/Els0IJVjFV RLke3SegTHxHncA8+BYn2k/VnTKwDXzP0ZLyc7mUbDl8CCtWGGUkXpaa7WyZIA/q mvUqh7671Vr4vJlq0kFbUibsFblZjk9uydHvvqaVpmBzbr/gWDyirHXwPl5lCnWp ORjT7tc8hjyt+dxpmnGdqlDIcqUjdCWoN6NxffLtKz/XpJ+dBvA8rXT/QaPSaVCG o0DbgybvRF1HvX30udx4FF9fFsVAbYP1mvZx4fHy+Z1rJJhODZv1YpH7YY1bmG02 vfFkwpW4AyAdsONA+n/XdMCsA006/pljNd3GxjcqB5D6BhpdUvcgUslkuELsVYWb EyhxKzzJvZNjQ/iHsaThooy9SFHc71PgYdyEL/WzoGr421GwpCL6BuE0rlumgaTm joU/9ydLO6zpbV4RYDgtsaGQxOxVc0y1Lj8CWTi/XYIVRnmqrjGmubRV7q8pTxrg oyk2zwQ+twyxp/8ZRHzl5ISiDLKSDlcMK1oa7NqyL+MCwiswpaObk56HxgF2ZwEb JZYCwetxyTK7HX4/WV0V6TaPzS7dHAsb6t1Aq8IS1JdGjWKRPkjkhR95nQARAQAB tCNQYXVsIFNjaGF1YiA8dmFuaXRhc3ZpdGFlQGZzZmUub3JnPokEwgQTAQoCrAIb AwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4ACGQEWIQR/kRb+qQpZg5NsfPqgJ9sv Ph4RigUCYAwbLDUUgAAAAAASABpwcm9vZkBtZXRhY29kZS5iaXpkbnM6amFiYmVy aGVhZC50az90eXBlPVRYVD4UgAAAAAASACNwcm9vZkBtZXRhY29kZS5iaXpodHRw czovL2Zvc3N0b2Rvbi5vcmcvQHZhbml0YXN2aXRhZZAUgAAAAAASAHVwcm9vZkBt ZXRhY29kZS5iaXp4bXBwOnZhbml0YXN2aXRhZUBqYWJiZXJoZWFkLnRrP29tZW1v LXNpZC0yMDkzNjgxNTQ1PTYyODlhYTNiZDhhNTAxYTM2MzIyYTBmODk0ZjhkMWQ5 NzE4ZGVkMDM2MTYwMzlmMWNmNDhiMmE0MWVlMzU5MjCPFIAAAAAAEgB0cHJvb2ZA bWV0YWNvZGUuYml6eG1wcDp2YW5pdGFzdml0YWVAamFiYmVyaGVhZC50az9vbWVt by1zaWQtMTk5MTQxODIwPWY0YThmZjg0MDA0MzkzYTg3ZjcwMTNjNjAwNjViZGM4 OWIxMTY5ZWJjZmI4MDYwYzRmOTY2OWI0M2JhMGM4MTSQFIAAAAAAEgB1cHJvb2ZA bWV0YWNvZGUuYml6eG1wcDp2YW5pdGFzdml0YWVAamFiYmVyaGVhZC50az9vbWVt by1zaWQtMTQyOTY3NzEyNT1lOGE3YjEyMzZiODUwYjQ2N2E1MDkyYzBiZGZlYTg2 YTUzZTM2ODQyODNhMWQ1ZmUyNmVmNTg3MmRkMGFlZjQxSBSAAAAAABIALXByb29m QG1ldGFjb2RlLmJpemh0dHBzOi8vY29kZWJlcmcub3JnL3Zhbml0YXN2aXRhZS9n aXRlYV9wcm9vZgAKCRCgJ9svPh4RivdTEADC3xMcrcDR/+4JlDl5fblecfJHr3/E 0fzkPWJJBL+TIn3ON2sSKIfLn9M7NYWIGT0QLI4LnqT+SZ3Ont1h8irM4O8LuTwZ kqjLkytGhgCErSdGzJ3oIcdXcnzX/p6fmxer1Qg/bpFy8mRrpSQ5tI0TYUXfD0qs BEbUhB3Tsg8AYaDRcdPx8gf1METZDxx/E6RQNzVIfyCK8hszzU1pRFr15DYDCjl5 RZjTxXqxJFKUz85LvQToaFo5SXgH/fWf0EeoD+YNqyhROYr8iWMLCLiHqvqkEXny lm7qNlFxFGFSu8Mcj6HSet5qvRj2wn6XssOWm2pOalDJx+L/biETr5vEnBwfw7p2 1Pmrg/jhK9yasKsdYKRlJdJWOtpEi9amcQ4sGA9OD74weJ/zEEPgLKbvkWFuUy8a 69AEeKAbB3RH3r7+PRnPVvxC3MpEmLsRsjVdP21xGhtnqAzJFkMRXf5lpC6czJiH gd/sao0mJPrkWUHDn0k9rgoZI9gRRENk3tXefjwQ2A5aEcAagmb2l0DjugYAb7dU ip9bJNUhBgjiaWYBj9uZOzYdQ7kFcFWp7iCGvkoeBMQf29rXZOZsxQmKLgEPZuCl YmIO4PS6sERoPT+FUGl85YAkEIBII0TCQdVQd/Vx6JRLc/f/cFCoKBv2+9LKVPIp wNNL5J+0m/H1dLkCDQRX89bnARAAs1NzkaHRNHWu2YiQk8lTctciFjyMlVH/Vy28 yZSfpHWrt7MCzhkaK1PYsWlnJifOlCnvzyDW26ouLqbPR51lzRFs9UID1dzg4RCu PMs0TwlIfcUCbBRc3lq3An941sEwD0+gguGog1oIum2regAftnbSoQj/1+OoZZz0 zqeDkHorQcCDTc3EfYsLjswiFioioOPWgPjG6DSa39xf07YdrW0DOwpJ/M+MCVoP xREqbXC/oCYUQ85h4V66a8YMYrmkeHzq1kuX7HXuoJKtX8W3vHCiPo/sU/wF74b0 oDiskfeXwMaZoRhVPkYGBEIhAO6n9tqWtuSzxWmMWH/TDw8h2GM6hCa67YPVuiTn ztNdr8FR9D3WFpcizpbNJFj6HBcrfO6IwD5NK8h5fiqFeIQAIfo1PL88OC8jDVjs cF0YoJeCiI8sRFjP/1y/MbYaKIR4fA+PbogeW/klGeI8bp49dGQa+8cnrgDcnzNS 1TXh1Zcaob9H+DDHdSCN37hHtfroFDBCr6KRQ55WzBTdR+zmibZDjkGY4T0uaQjF QAGshPNGcr63rCSWyZnInx1H4WWwnsUquTt7T+qt0TAOfd+9shgPqz/dLKkkF87m BtS423dGdDp6BZJ5t4lpl8LGiSuk9p/ckoB4MET+1iLjaU+FECLFyIg95v6Gk1OY FxeDnnEAEQEAAYkCfgQYAQgAcgWCX/iQQwkQoCfbLz4eEYpHFAAAAAAAHgAgc2Fs dEBub3RhdGlvbnMuc2VxdW9pYS1wZ3Aub3JnYWATd/tucGd3FDiHb4AJdZ9NptbA cccakj1mpmFlMEkCGwwWIQR/kRb+qQpZg5NsfPqgJ9svPh4RigAAMB0P/RLNvisc aB3Ii0ZLMs6wQOsYkJ/O1c4fm8ajmz+Z5lgEhgVbeFhmsqJHIgk/ni4UcdHAsKIB wfcVxZPzR+nH1g5CId/E2mZXCcCi586Z8jyn8b34Vx/rYdJVkqyBL3OtS+EOMBRO vA5VsNWrIVm0BrGqzEjm0mKUuRldpZyjNRzD2beITJkOCk1H/Vqt+bCXmxb2akb+ 06bB0NqKG+kjRvlCnSwBvZ+RyiXVrOeeoj4ODgGyta0W+Rtnoa+AXpr5JE6uBc3Z +vgZrDndqBgD/SZUXjNC//Y3M6qxfji84e8HXmFzuZccmSzwH+Op6Mlh4XiPhqxm L5/AJoE8QxCUnCb4mENcnfGdmnlmWGrbApNkdmb3hXDXpZCJzRYgdPtUEuWJ5/ml m0979/bF8b0HN0eCG06VqoNi+nSNbeth7f/4gseq60DpcJaf4lGVs9AgjXFNGWSy ZmHuFwM+UpfHZiRXfprbilB7ZBhfhx9d0MZ7luyFAa1IdCjb3bpdvZMPSSx8xoW4 obcuExVayJzJz1HCeWwr3wYuzV4SkWbSm3YWOBfK9EaGc2RogTu89esmyCwW2usl cSrnYS6Dp0lCcC1CXsKlZKWV2GZgbZAUI+w7T71UT4Dw/P4qOvuKIfqvD2SJ0Zfo KoV1oa5YNHqpsJUmmc+UXmfTZgfP14xzBUyV
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/CDn5XT-osvo9yCeOy2_j9IottH8>
Subject: Re: [openpgp] OpenPGP certificate structure: multiple binding signatures on subkeys? (MR 43)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 21 May 2021 18:14:22 -0000

------=_Part_10_180247185.1621620852991
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

SGV5IGxpc3QhCgoyMS4wNS4yMDIxIDE5OjI1OjE5IERhbmllbCBLYWhuIEdpbGxtb3IgPGRrZ0Bm
aWZ0aGhvcnNlbWFuLm5ldD46Cgo+IEkgbm90ZSB0aGF0IGlmIHRoZSBjaGFuZ2UgaW4gdGhlIHN0
cnVjdHVyZSBpcyBjb3JyZWN0LCB0aGVuIHRoZSB0ZXh0Cj4gYmVsb3cgaXQgc2hvdWxkIGFsc28g
YmUgY2hhbmdlZCAoaXQgc2hvdWxkIG5vdCBzYXkgImhhcyBhIHNpbmdsZQo+IHNpZ25hdHVyZSBh
ZnRlciBpdOKApiIpCgpHb29kIGNhdGNoLCBzaGFsbCBJIHVwZGF0ZSB0aGUgUFIgYWNjb3JkaW5n
bHk/CgpBbm90aGVyIFBhdWwK
------=_Part_10_180247185.1621620852991
Content-Type: application/pgp-signature; name=signature.asc
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename=signature.asc

-----BEGIN PGP SIGNATURE-----

iQJBBAABCgArJBxQYXVsIFNjaGF1YiA8dmFuaXRhc3ZpdGFlQGZzZmUub3JnPgUC
YKf4bwAKCRCgJ9svPh4RisEyD/4nRvy+QGNJm9vrtyY7JR89igJSAiZzCS6eCAkE
QIhxam6TPWVTc+SCeqbgrQdA75oTqSanRTf7rJKLoOMPle0y8hVPiyD9q1gz/eYc
VbF93qfg6T085vYDc9Tp0Nj7s6gAalGuqROqEJp/Mb+UADoBVE5q+E02q/swo5MU
jFc2+i6yIjg9OISNk/Z3jiLkebj0lxRCzZlelF/RmaCZ5s819gZrXImTMsyZFL+F
6U6yuzKEO+ZkgYmOMfqJZLdMQS7phaVlO4O3+9kPTH2STraRqzA+NnR1gvQ0Wbmn
rz58CoNV7dh2FZPBcKoYzi+ILi5yLCUJWmnstAGJqZWCUPk2SMS7WssQaJsv12D3
U99jYp1Enl17OmynOF+pam5HzrMasMocPqsIzxblavM4cHkNI69G540nwtv6CNha
/E1mLxqaWybtOLNGm828s71mLZszeDKpZgkth7ZwTvCD1jXPrq0DZMyq9Hz5/LZn
DAQJNZAk321ItdnHY2+Xx+9XgcmaTdkmA4zOCFNQxOaMQjoqGfi06N5ji/6HuZmy
IhOemt41+1I3vBca3ZZNtY+YDbvgDVm3+grCfCe38wfGiVBZxNVl7XlYYlpnzbgq
GxV7/5AvMhUIH3vOmMFgiu6LeXf2BuSq6kF0OM3CTss5ppIHb4HANBhvxX+l0Cro
J/htzQ==
=iQWZ
-----END PGP SIGNATURE-----

------=_Part_10_180247185.1621620852991--


From nobody Fri May 21 13:18:46 2021
Return-Path: <sandals@crustytoothpaste.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 845073A1F3B for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 13:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (3072-bit key) header.d=crustytoothpaste.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2mgF7letltz for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 13:18:40 -0700 (PDT)
Received: from injection.crustytoothpaste.net (injection.crustytoothpaste.net [192.241.140.119]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EAAE3A1F39 for <openpgp@ietf.org>; Fri, 21 May 2021 13:18:39 -0700 (PDT)
Received: from camp.crustytoothpaste.net (unknown [IPv6:2001:470:b978:101:b610:a2f0:36c1:12e3]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by injection.crustytoothpaste.net (Postfix) with ESMTPSA id 7A0ED6043F for <openpgp@ietf.org>; Fri, 21 May 2021 20:18:08 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crustytoothpaste.net; s=default; t=1621628288; bh=y6CfffZFM6pUFDMSzgBhgXGz7Ay3i069DPzkcW6KNek=; h=Date:From:To:Subject:References:Content-Type:Content-Disposition: In-Reply-To:From:Reply-To:Subject:Date:To:CC:Resent-Date: Resent-From:Resent-To:Resent-Cc:In-Reply-To:References: Content-Type:Content-Disposition; b=WNnRHNfnelzmUElPV0A5jSe2nzGKiqSSjCYDphKwcKJVKiDo/gqseYqFEYq0Abq1j KAeDnTiplOmNQwMSnhnS+sj6EsrTXhuaskr+nEhOJNhMRri9RTotUhrqYBt/7ld+vj Q7ZpcDBkPSVHnELn5YU5YzWu5RpjNWrBjAsuJsS64F7dBbY/F8WGG09cefBJp4gdwe BDi18k7WTOKlFaryhHwdjrv6wOHZswTQDF8Fx5BSHXE6Uag6d2InHmBPgL5/eqD8+O l3EVWckN3doxloOd4YyXPAup/ipiBMHfQ5878AcWDLoEjEyh2ikDTJUnUVRffc2FTT ZtXD8rBJo4RThq+jK18T9b+5h0UX3mW77E1N9d2QQfdUWLHwuSUzz+C4mtj5sF4k9e kiOIIFxSsqhhMtX8nWGeZH4JRWLbD0wKIOQU7RZsGOWkuujPQw+L3a8EEIfj5dj/Kl K+OP3cURqlVCzBalX9JKvPO/tG//mMT+TX5hC/1ptBhLIkhGkUW
Date: Fri, 21 May 2021 20:18:02 +0000
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: openpgp@ietf.org
Message-ID: <YKgVesA8U+EKgboS@camp.crustytoothpaste.net>
References: <878s48dlkn.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Tc5nHcMBw2N9dKUQ"
Content-Disposition: inline
In-Reply-To: <878s48dlkn.fsf@fifthhorseman.net>
User-Agent: Mutt/2.0.5 (2021-01-21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/yOWCGY2P0JUAJmJOpE-ZBuBrumo>
Subject: Re: [openpgp] Ed25519 and digest choices (issue 31)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 21 May 2021 20:18:45 -0000

--Tc5nHcMBw2N9dKUQ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2021-05-21 at 17:48:56, Daniel Kahn Gillmor wrote:
> Alternately, maybe we should instead reframe OpenPGP's use of Ed25519 as
> a "PureEdDSA" scheme that signs only the OpenPGP digest (not the signed
> data directly).  That bypasses the "PH" parameter, but it also means
> that any cryptanalsis that is applied to EdDSA isn't necessarily
> applicable to OpenPGP, because we have this additional step involved.

I would prefer this approach.  OpenPGP has traditionally allowed users
to use whatever digest they like with keys, even when the standards have
traditionally fixed a digest.  For example, DSA generally has specified
that either SHA-1 or SHA-2 has to be used and it has to be used with the
proper size q, but we've allowed RIPEMD-160 and SHA-256 with smaller q.

If, for example, we discover a weakness in SHA-512, it should be fine
to switch to SHA3-512 for signatures without problems.

I will admit that using multiple digests may require additional work for
cryptanalysis, but I suspect that if PureEdDSA is secure with arbitrary
messages and the hash function is collision resistant (both of which we
would reasonably expect), then this approach will likely be secure.  I
provide no proof of my conjecture, though.
--=20
brian m. carlson (he/him or they/them)
Houston, Texas, US

--Tc5nHcMBw2N9dKUQ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.3.1 (GNU/Linux)

iHUEABYKAB0WIQQILOaKnbxl+4PRw5F8DEliiIeigQUCYKgVeQAKCRB8DEliiIei
gccfAP9NLpb30oSfRcPqmMpznDjqvEw+wSbTfakKgkNqLt4F1gEA8+jlsb8Nhoyc
BabFDB1ZAo3UK4gZcREY+quBKKPC0QY=
=E051
-----END PGP SIGNATURE-----

--Tc5nHcMBw2N9dKUQ--


From nobody Fri May 21 15:13:50 2021
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 2BFEE3A229D for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 15:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=af9MLiUJ; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=4X1+HGdQ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xYzfEf9K7KLX for <openpgp@ietfa.amsl.com>; Fri, 21 May 2021 15:13:43 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [IPv6:2001:470:1:116::7]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BE093A229A for <openpgp@ietf.org>; Fri, 21 May 2021 15:13:43 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1621635221; h=from : to : cc : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=MDqgAQ7IueSWKwcqw8CcR0aACmO1qS2iVKzW0iW2tq4=; b=af9MLiUJumBqnSerWHatWb/cakeUDdnMrVqjh7L0u7jVwj03sF6aiddkCwscNfqqxj+SA CkW3iZ8pnI/yEnLCQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1621635221; h=from : to : cc : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=MDqgAQ7IueSWKwcqw8CcR0aACmO1qS2iVKzW0iW2tq4=; b=4X1+HGdQmW8EQP5I13H3NG/HCNE7A1xjCFiQH1RSt9S8+LvKZncuBGhSqcOVXJc0IR2P8 ggZIFNH9KOSbVXvDh2X1drcuepuEGYM51dVVP3Fr65t1kY5RTbqWf2McjPKJLrWuYuWUwCk BB+RnMrZbvYqFBhv/MZzIyvDecvuEssVqIHtCWyKNevH5bv9UcB5MCMYExMFWG034lHyCvW f8K4WXjVyhye2UYeBdGxq5eDDEnGO2Q5Wlphp8juQ6Z3S/G/TBNpBJ93TbJApamPsz03usI MknJVrmVOb7hCxSxzBy5hGsPLXGQ6M1bpYFmLpMsK3x284ctU4I/JEdDGqCw==
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 RSA-PSS (4096 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 5D8E7F9A6; Fri, 21 May 2021 18:13:40 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id CCB582040E; Fri, 21 May 2021 18:05:36 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Paul Schaub <vanitasvitae@fsfe.org>
Cc: openpgp@ietf.org
In-Reply-To: <076a1bac-b6c5-4975-8c24-e5c90ffbd5be@fsfe.org>
References: <87bl94dmov.fsf@fifthhorseman.net> <076a1bac-b6c5-4975-8c24-e5c90ffbd5be@fsfe.org>
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, 21 May 2021 18:05:35 -0400
Message-ID: <8735ufeo9c.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/TeaQ1_uqhwDFMThj9JraRa8pkng>
Subject: Re: [openpgp] OpenPGP certificate structure: multiple binding signatures on subkeys? (MR 43)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 21 May 2021 22:13:49 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Fri 2021-05-21 18:14:12 +0000, Paul Schaub wrote:
> Hey list!
>
> 21.05.2021 19:25:19 Daniel Kahn Gillmor <dkg@fifthhorseman.net>:
>
>> I note that if the change in the structure is correct, then the text
>> below it should also be changed (it should not say "has a single
>> signature after it=E2=80=A6")
>
> Good catch, shall I update the PR accordingly?

Yes, it'd be good to have the MR present a coherent change for folks to
consider.  Maybe rebase it against master while you're at it?

Thanks,

       --dkg

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYKgusAAKCRA+nXFzcd5W
XLvAAQDJG/TNSsHbtLHC9p+LCwzEofRFJgF9cfRRsp4cT7J26wEAy2Q9EBkGP7gF
lQsaCnOPwswydhSZdWY54PqQcigigQI=
=OiiR
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon May 24 09:00:31 2021
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 B1E513A2D7D for <openpgp@ietfa.amsl.com>; Mon, 24 May 2021 09:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level: 
X-Spam-Status: No, score=-1.306 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, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=SNr2UIxB; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=By5FVmrr
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cq0FwRTg6fMd for <openpgp@ietfa.amsl.com>; Mon, 24 May 2021 09:00:24 -0700 (PDT)
Received: from che.mayfirst.org (unknown [162.247.75.117]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCDC53A2D78 for <openpgp@ietf.org>; Mon, 24 May 2021 09:00:24 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1621872021; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=1du2B2LWWhRYdoI4GXB8QUx4iz5NIskiXiJfd0aZOEY=; b=SNr2UIxBRbDnsRKgqJNJSWmuAVGpvr7OlQFqrJ3adPtKRckhjpz0j/8x+u0st0XpwWGY+ KLpC3zii0jBLWTYBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1621872021; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=1du2B2LWWhRYdoI4GXB8QUx4iz5NIskiXiJfd0aZOEY=; b=By5FVmrrJDR3EZFdaKzQJBRTJXSgaglRCA+EaCnn4XT4MyqBIeIUxMIZ+tyb2kUGFBQYu yKFRaDnOa4Taad61sOyrlnbd/KAdo0v9WA2IFPYxrpZ6uLOmKh5fyyjTgJxwYZzo0QieKMl vwl4AtGqAtPqcrVS7Pfm4hNLEbLhztiABBDtGWR5CXj39pkncBc4E/ghb8U2/DWSRk/tKZw UCYWT2UY7ZpmxyVFsAxJUDeXtPB2OFGe0S/504XKE3QxY5mmKpG+K8VliBjAaX6JywKdIMR oMldvBT/nW5yH+fpSG2iJ1QSAXQkA2uunSDkCsaIOD07wnmQ2v5qyILZ938g==
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 RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 344F4F9A7; Mon, 24 May 2021 12:00:20 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 7CC1121D0C; Mon, 24 May 2021 11:58:42 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>, openpgp@ietf.org
In-Reply-To: <YKgVesA8U+EKgboS@camp.crustytoothpaste.net>
References: <878s48dlkn.fsf@fifthhorseman.net> <YKgVesA8U+EKgboS@camp.crustytoothpaste.net>
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: Mon, 24 May 2021 11:58:41 -0400
Message-ID: <87r1hwcedq.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/P0NYp2OjKDsv5ReCJvn-XEm5vtE>
Subject: Re: [openpgp] Ed25519 and digest choices (issue 31)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 May 2021 16:00:30 -0000

--=-=-=
Content-Type: text/plain

On Fri 2021-05-21 20:18:02 +0000, brian m. carlson wrote:
> On 2021-05-21 at 17:48:56, Daniel Kahn Gillmor wrote:
>> Alternately, maybe we should instead reframe OpenPGP's use of Ed25519 as
>> a "PureEdDSA" scheme that signs only the OpenPGP digest (not the signed
>> data directly).  That bypasses the "PH" parameter, but it also means
>> that any cryptanalsis that is applied to EdDSA isn't necessarily
>> applicable to OpenPGP, because we have this additional step involved.
>
> I would prefer this approach.  OpenPGP has traditionally allowed users
> to use whatever digest they like with keys, even when the standards have
> traditionally fixed a digest.  For example, DSA generally has specified
> that either SHA-1 or SHA-2 has to be used and it has to be used with the
> proper size q, but we've allowed RIPEMD-160 and SHA-256 with smaller q.
>
> If, for example, we discover a weakness in SHA-512, it should be fine
> to switch to SHA3-512 for signatures without problems.

well, it's true that we could swap out PH(x) (the prehash function) but
if i'm understanding EdDSA correctly, we could *not* swap out H(x) (the
hash function), which is SHA-512(dom2(phflag,context)||x) for any
variant of Ed25519.

see https://datatracker.ietf.org/doc/html/rfc8032#section-5.1 for more
details about the EdDSA parameter choices for the three different
flavors of Ed25519.

If i'm understanding how OpenPGP uses Curve25519 for signatures
correctly, I don't think that the OpenPGP choice of digest has any
effect on H(x).  If it does, it's hard to say that we'll have dodged a
SHA-512 weakness entirely.

> I will admit that using multiple digests may require additional work for
> cryptanalysis, but I suspect that if PureEdDSA is secure with arbitrary
> messages and the hash function is collision resistant (both of which we
> would reasonably expect), then this approach will likely be secure.  I
> provide no proof of my conjecture, though.

I have the same intuition as you, and the same lack of rigorous proof :P

  --dkg

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYKvNMgAKCRA+nXFzcd5W
XERkAQDemN/l2o+CfyPFNyrq4nPMHv/s3OBU4FmjqKouzCmexwEApoYRe12FTHGi
hMWmwF+HVxbW5JY4kK6dkgXG3P4kJQ0=
=MdeP
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue May 25 00:37:31 2021
Return-Path: <wiktor@metacode.biz>
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 8BEDC3A194C for <openpgp@ietfa.amsl.com>; Tue, 25 May 2021 00:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=metacode.biz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-scq-S9H5R7 for <openpgp@ietfa.amsl.com>; Tue, 25 May 2021 00:37:19 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40F6C3A198F for <openpgp@ietf.org>; Tue, 25 May 2021 00:37:14 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id y184-20020a1ce1c10000b02901769b409001so12240350wmg.3 for <openpgp@ietf.org>; Tue, 25 May 2021 00:37:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metacode.biz; s=2017;  h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=Zhr4Y0B1zpykQXLY0PvdY6RhKP01gKwufIB76Nr4eUk=; b=HvyxEoiGDgJEhIvhO+jShads3fur7zkhKe7EzTpjm5uq3z1tf3nyKhEAEWdgLa0IQ4 avfVg3hQ6sz874dfgSAJxJWWq1jixUvHIqoatlNpsk+F6Hj3iKvVQmC5oJXKNuKJjMB1 B5fKxgPwskB61kCC9UhQjyg/TBOwpo+qQ0THx3LqjcNMcnvRuUnYIqJsYv2x2CJNBZJf JDqMQwsyQwmsAGoPSy6SNUl0mV7hiRm1tut8x5jmRHVt3Y4v6PqGQX4zmYU74jr44wFE pK1WtYg3gKHA0b2Xd0ClONarBsTrG1630Axy83e5z8VKxzHj/l/AJBLtKmJxojdpKwd2 X99Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=Zhr4Y0B1zpykQXLY0PvdY6RhKP01gKwufIB76Nr4eUk=; b=IIYzR38YdB5qdTPNlnOwNKJuCZZii6Yepp9hgZY3IcQHR6WzKtqoOZvOTA7Y/cdZd/ lXAtoOowJyylTkLVuxPBUxiI4boob++FR+Gvi1/a+zOkpGuGqEQKST+AZfIiHiM6VigR NVQCNJSiyGRyqaz3VJ7GHskbOFrUgqBHPd2NyGubB3VIw5H81oNOLYEGxFjxEh3v9WkZ OaU2G5XNgwI1QX0TxZ57TOvRTPpCAjoTkjcbxv1hnsPTR9DS1HZgVHvv83i9luzckQRh n2EpIGt8D/9SoFK4uCvbfohuF2SggjucoUenC3c+9ZAVJ4HQ+lDSSGlhs+wDFOnkMzm5 g2/A==
X-Gm-Message-State: AOAM533YkDNz6ty4DZCZHF7vhhVLxQ6jYImPWqS3KVdNYjxr8K8SNu0M xBH9Bz9RFtXHK/e+0nJV1gbyuvfcEUhCTw==
X-Google-Smtp-Source: ABdhPJzxPjkI3WPK35zXYQYS4Zfo1DUjfha9zI8U8j4CvPlMywy5PfmIdgTbdXsfdUkiHa4/A2Yc7g==
X-Received: by 2002:a1c:7909:: with SMTP id l9mr2597434wme.129.1621928231901;  Tue, 25 May 2021 00:37:11 -0700 (PDT)
Received: from tungsten (public-gprs408557.centertel.pl. [37.47.227.46]) by smtp.gmail.com with ESMTPSA id d14sm8615853wra.5.2021.05.25.00.37.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 May 2021 00:37:09 -0700 (PDT)
From: Wiktor Kwapisiewicz <wiktor@metacode.biz>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: openpgp@ietf.org
In-Reply-To: <878s48dlkn.fsf@fifthhorseman.net>
References: <878s48dlkn.fsf@fifthhorseman.net>
Date: Tue, 25 May 2021 09:37:22 +0200
Message-ID: <8735ubs1ql.fsf@tungsten.i-did-not-set--mail-host-address--so-tickle-me>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/XGLRWsL_RW-vnAkPqauP3q42bD8>
Subject: Re: [openpgp] Ed25519 and digest choices (issue 31)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 May 2021 07:37:30 -0000

Hi Daniel,
> Either way, it seems that we need to clarify the standard.

I agree. I've been working on a specific use case (decryption and
validation of messages when public parts of the key are unavailable) and
the amount of cryptographic agility here is, in my opinion, unwarranted.

>From what I can see SHA-256 is the most prevalent hash for ed25519
signed messages now but I see no problem in SHOULD'ing SHA-512 to align
with existing standards.

Kind regards,
Wiktor


From nobody Tue May 25 04:00:04 2021
Return-Path: <d.huigens@protonmail.com>
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 374423A0BC7 for <openpgp@ietfa.amsl.com>; Tue, 25 May 2021 04:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=protonmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BH2jpMWmVQed for <openpgp@ietfa.amsl.com>; Tue, 25 May 2021 03:59:57 -0700 (PDT)
Received: from mail-40136.protonmail.ch (mail-40136.protonmail.ch [185.70.40.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B8203A0BC1 for <openpgp@ietf.org>; Tue, 25 May 2021 03:59:56 -0700 (PDT)
Date: Tue, 25 May 2021 10:59:39 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1621940392; bh=ReZtJEvC7SifI182yyl0U6DvrCR7PNJS69suRHL6EHE=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=GyO/fqEwbjAJVyaxKrIEsKc94lSBXFe/Buu45zMIJ/7wSZjlvnVWwqAheENuSlq6a nc4iGTfLE/QKM4JxbyBQMEJmRUf1hxAYLZx+kdeAZAZafRYVsuRXsomh+Psf7HnrZP Bds5o5Ng3VpWgFi0K2+OqNeTwJmNsRchQAprhHUk=
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
From: Daniel Huigens <d.huigens@protonmail.com>
Cc: openpgp@ietf.org
Reply-To: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <cDduF8iIyBpPqMQ4JSZd7oYr0LSm3_L60OnGDrzoMFqD-gNYT0oZQeONgcjfmOwwy78LiPB7ifFi2K1rPOts-bBh15sO4UF4vJPI5yZSMkI=@protonmail.com>
In-Reply-To: <878s48dlkn.fsf@fifthhorseman.net>
References: <878s48dlkn.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/dLjaUhhN_jjK8VVFQ8vmCbNxfNo>
Subject: Re: [openpgp] Ed25519 and digest choices (issue 31)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 May 2021 11:00:02 -0000

Hi dkg,

I believe there's some confusion in the original issue.

https://datatracker.ietf.org/doc/html/rfc8032#section-5.1 says that:

   Ed25519 is EdDSA instantiated with:

   (...)

   |   PH(x)   | x (i.e., the identity function)     |

This is the function that the specification should (and I believe
tries to) reference. The OpenPGP specification indeed pre-hashes the
message as well, but this is irrelevant to (and comes before) RFC8032,
PH(x) is still x. There should be no need to reference PureEdDSA.

Best,
Daniel

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90

On Friday, May 21st, 2021 at 19:48, Daniel Kahn Gillmor <dkg@fifthhorseman.=
net> wrote:

> Over on https://gitlab.com/openpgp-wg/rfc4880bis/-/issues/31, jethrogb
> writes:
>
> > Appendix A contains an example for EdDSA. The example states that the
> > hash function used is SHA2-256. The example also states that the curve
> > used is 2b06010401da470f01, which is defined as =E2=80=9CEd25519=
=E2=80=9D elsewhere in
> > the draft. However, RFC 8032 specifies Ed25519 as an instantiation of
> > EdDSA with specific parameters, one of which is that H is SHA2-512 and
> > PH (in the ph case) is SHA2-512. Is it the intention that OpenPGP
> > implements not Ed25519 but some other form of EdDSA? If yes, this
> > should be called out explicitly in the text and it shouldn't be called
> > Ed25519. If no, the example needs to be updated and it would probably
> > be good to explicitly call out Ed25519ph in section 14.8.
>
> How does the WG think this should be resolved?
>
> I intend to sign this message with an EdDSA signature from a Curve25519
> key, but it will likely use SHA2-256 as the OpenPGP digest choice (in
> the EdDSA RFC 8032 framing, that would be the pre-hash "PH" parameter to
> EdDSA).  This would mean that we are *not* using Ed25519ph, since
> OpenPGP permits variance of the PH parameter.
>
> One approach would be to clarify that OpenPGP signatures made with
> Ed25519 SHOULD use SHA2-512 as the OpenPGP digest, which I believe would
> align it with Ed25519ph.  But there would still be existing signatures
> out there (like the one signing this message) which would use SHA2-256,
> and it's hard to say that signature verifiers should reject those
> signatures.
>
> Alternately, maybe we should instead reframe OpenPGP's use of Ed25519 as
> a "PureEdDSA" scheme that signs only the OpenPGP digest (not the signed
> data directly).  That bypasses the "PH" parameter, but it also means
> that any cryptanalsis that is applied to EdDSA isn't necessarily
> applicable to OpenPGP, because we have this additional step involved.
>
> Either way, it seems that we need to clarify the standard.
>
>        --dkg
> _______________________________________________
> openpgp mailing list
> openpgp@ietf.org
> https://www.ietf.org/mailman/listinfo/openpgp


From nobody Wed May 26 08:56:04 2021
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 7D26D3A0033 for <openpgp@ietfa.amsl.com>; Wed, 26 May 2021 08:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level: 
X-Spam-Status: No, score=-1.306 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, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=NJJTk30h; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=Qs3HnPA+
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQDcmLD_qVok for <openpgp@ietfa.amsl.com>; Wed, 26 May 2021 08:55:57 -0700 (PDT)
Received: from che.mayfirst.org (unknown [162.247.75.117]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74B343A32F9 for <openpgp@ietf.org>; Wed, 26 May 2021 08:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1622044556; h=from : to : cc : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=9CbQwRrV8PcvMmA2H51tlDHjhT1BiLuLDdPzOA5Bk74=; b=NJJTk30hPXuVzKWIbcQCiqqqrsSBZXSCT/uj7QJXc02W3Dh/9+pJU9gaartT69NTFMrc2 uRszlFYj95wukEAAw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1622044556; h=from : to : cc : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=9CbQwRrV8PcvMmA2H51tlDHjhT1BiLuLDdPzOA5Bk74=; b=Qs3HnPA+IgdxgtNjPZEoY1LC3gx+11bb5lHFj6THNEy5P1hOzw3m0v3Ufr5ArfAh/jj7F imrf3UHgNfC9/i5AxuP6LDSviZi8ufoDlOseoBVvcAaMlkmpl9K88t0s3Sh/Vs33ddVjSrv dJWbU7A/qrw81nB2mdKJhGlddsagcDm8PdEAdSYbk8X05fNCmzzkUs8WwsXYIWgWHWP9iSQ PMb27kc/+ChBoPnnDEXbkv49uh/+xyJRuMbQBSPy+yGuFVFyKuK0BHZL0V4RMFyMNTO3keE J3gg9Wq+XDOM4JjZ3rk8JVPu+td5c7qjS3yCbXn7thMPpVUchtETRQZJCoHg==
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 RSA-PSS (4096 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 3D31CF9A7; Wed, 26 May 2021 11:55:54 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 1D765204CB; Wed, 26 May 2021 11:55:53 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Daniel Huigens <d.huigens@protonmail.com>
Cc: openpgp@ietf.org
In-Reply-To: <cDduF8iIyBpPqMQ4JSZd7oYr0LSm3_L60OnGDrzoMFqD-gNYT0oZQeONgcjfmOwwy78LiPB7ifFi2K1rPOts-bBh15sO4UF4vJPI5yZSMkI=@protonmail.com>
References: <878s48dlkn.fsf@fifthhorseman.net> <cDduF8iIyBpPqMQ4JSZd7oYr0LSm3_L60OnGDrzoMFqD-gNYT0oZQeONgcjfmOwwy78LiPB7ifFi2K1rPOts-bBh15sO4UF4vJPI5yZSMkI=@protonmail.com>
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: Wed, 26 May 2021 11:55:52 -0400
Message-ID: <87mtshbibb.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/sB9IvxIZwuK8lCjt2asoIGMFFsU>
Subject: Re: [openpgp] Ed25519 and digest choices (issue 31)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 May 2021 15:56:03 -0000

--=-=-=
Content-Type: text/plain

Hi Daniel--

On Tue 2021-05-25 10:59:39 +0000, Daniel Huigens wrote:
> This is the function that the specification should (and I believe
> tries to) reference. The OpenPGP specification indeed pre-hashes the
> message as well, but this is irrelevant to (and comes before) RFC8032,
> PH(x) is still x. There should be no need to reference PureEdDSA.

https://datatracker.ietf.org/doc/html/rfc8032#section-4 says:

   This document specifies parameters resulting in the HashEdDSA
   variants Ed25519ph and Ed448ph and the PureEdDSA variants Ed25519 and
   Ed448.

So the non-prehash variant named Ed25519 is indeed "PureEdDSA" -- but
it's being applied to something other than the user-visible "message" in
the OpenPGP context.  Maybe we don't need to reference PureEdDSA
explicitly, but the fact that "Ed25519" is often used as a shorthand for
the whole family of EdDSA mechanisms over curve 25519 introduces some
amount of ambiguity in the spec as it's currently written.

I welcome suggestions for text that clarifies this subtlety in the
draft.

        --dkg

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYK5viAAKCRA+nXFzcd5W
XKm6AQC4egFotazn135AlbS/jGq4qR42Q1ju3G7xlmZcnr5OSAD/UA5YUqfHhDv9
lzN6dYnDxNTzTOyy2dlh13rSBe2dPwM=
=+dE3
-----END PGP SIGNATURE-----
--=-=-=--

