Re: [openpgp] To bind or not to bind

Andrew Gallagher <andrewg@andrewg.com> Fri, 22 March 2024 18:51 UTC

Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Andrew Gallagher <andrewg@andrewg.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 22 Mar 2024 18:51:30 +0000
Message-Id: <23B46D65-EAF7-43D0-A5F1-04D28B698559@andrewg.com>
References: <87a5mqi0xi.fsf@europ.lan>
Cc: Aron Wussler <aron@wussler.it>, openpgp@ietf.org
In-Reply-To: <87a5mqi0xi.fsf@europ.lan>
To: Justus Winter <justus@sequoia-pgp.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/7SzqOLcAaj3K_RhB42vNJVlYMxY>
Subject: Re: [openpgp] To bind or not to bind
Precedence: list

Hi, Justus. 

On 22 Mar 2024, at 18:20, Justus Winter <justus@sequoia-pgp.org> wrote:
> 
> - v4 OpenPGP implementations are not robust enough to handle unknown
>  subkeys.  Adding PQC encryption subkeys to v4 certificates is not a
>  viable opportunistic upgrade path, but a way to make your existing
>  certificate unusable:
> 
>  https://tests.sequoia-pgp.org/#Mock_PQ_subkey

Is it possible to update this test with the optional flag that Falko mentioned, to see if it improves RNP’s score on line 3? If it does, I’d argue that this is no longer fatal - gopenpgp v2 has been superseded already, and pgpy is fairly niche.

There is still a potential issue with large subkeys, so maybe we could test to see where the size limit actually is for each if the implementations that fails line 4? We may still need to RECOMMEND that only “small” PQC encryption keys should be used with v4; but for the purposes of early adoption, one algo may be enough.

A

[openpgp] To bind or not to bind Aron Wussler
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Johannes Roth
Re: [openpgp] To bind or not to bind Kai Engert
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Kai Engert
Re: [openpgp] To bind or not to bind Daniel Huigens
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Daniel Kahn Gillmor
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Daniel Kahn Gillmor
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Aron Wussler
Re: [openpgp] To bind or not to bind Kai Engert
Re: [openpgp] To bind or not to bind Bart Butler
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Daniel Kahn Gillmor
Re: [openpgp] To bind or not to bind Daniel Kahn Gillmor
Re: [openpgp] To bind or not to bind Aron Wussler
Re: [openpgp] To bind or not to bind Aron Wussler
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Daniel Kahn Gillmor
Re: [openpgp] To bind or not to bind Aron Wussler
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Kai Engert
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Aron Wussler
Re: [openpgp] To bind or not to bind Falko Strenzke
Re: [openpgp] To bind or not to bind Johannes Roth
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Nickolay Olshevsky
Re: [openpgp] To bind or not to bind Nickolay Olshevsky
Re: [openpgp] To bind or not to bind Falko Strenzke
Re: [openpgp] To bind or not to bind Werner Koch
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Justus Winter
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Bart Butler
Re: [openpgp] To bind or not to bind Michael Richardson
Re: [openpgp] To bind or not to bind Falko Strenzke
Re: [openpgp] To bind or not to bind Andrew Gallagher
Re: [openpgp] To bind or not to bind Aron Wussler
Re: [openpgp] To bind or not to bind Heiko Schäfer
Re: [openpgp] To bind or not to bind Bart Butler