From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: Fwd: OpenPGP interoperability issues with gnupg >= 2.4
Date: Mon, 6 Feb 2023 20:27:57 +0000 [thread overview]
Message-ID: <F30D6590-3E0C-4865-A944-7DE118A619CF@gentoo.org> (raw)
In-Reply-To: Y+FiAeD5eiuC0tMX@hmbx
[-- Attachment #1.1: Type: text/plain, Size: 3129 bytes --]
> Begin forwarded message:
>
> From: David Runge <dvzrv@archlinux.org>
> Subject: OpenPGP interoperability issues with gnupg >= 2.4
> Date: 6 February 2023 at 20:24:27 GMT
> To: tmz@pobox.com, ncopa@alpinelinux.org, tbier@posteo.de, sam@gentoo.org, demm@kaosx.us, mail@jann-roeder.net, cho-m@tuta.io, fpletz@fnordicwalking.de, rahul@gopinath.org, tpgxyz@gmail.com, jan.christian@gruenhage.xyz, dkg@fifthhorseman.net, eric@debian.org, xtkoba@gmail.com, dleuenberger@suse.com, adridg@freebsd.org, jjelen@redhat.com, anthraxx@archlinux.org
>
> Hi all,
>
> I am one of the package maintainers of gnupg on Arch Linux.
> DISCLAIMER: Since December 2022 I am also a contracted developer for the
> Sequoia project (an alternative implementation of the OpenPGP standard
> in Rust).
>
> We (Levente Polyak and I) are writing to you because you are the
> maintainers of gnupg on other downstream distributions.
> With gnupg 2.4.0 a change has been merged [1], which has gpg operate
> with certificate material in a way that is incompatible with the
> upcoming IETF approved "crypto-refresh" approach.
> This means, that e.g. messages encrypted using a key generated with
> gnupg >= 2.4.0 will not be compatible with OpenPGP implementations
> following the upcoming IETF standard.
>
> While this has especially integrators such as Thunderbird [2] and
> keyserver authors worried, it is also a concern for us as a downstream
> distributor of gnupg.
> Some of you have already updated gnupg to >= 2.4.0 in some form, but we
> would like to take the time and open the discussion on this topic, as we
> believe that the change is harmful to the larger OpenPGP ecosystem.
>
> We are currently still shipping 2.2.x due to (only now resolved) issues
> with our distribution keyring. However, we are wondering how to proceed
> with gnupg in the future, as it will also negatively affect the trust
> model of our own distribution.
>
> Several scenarios seem likely (depending on adoption):
>
> * notifying users of upcoming incompatibilities if they create a key
> with gnupg >= 2.4.0
> * shipping/ using gnupg 2.2.x alongside (or exclusively) for as long as
> possible
> * undoing the change in gnupg
>
> We would like to raise awareness and gather some feedback of current
> packagers of gnupg to form a broader response to this issue.
>
> As mail threads with large To: headers might get very tedious for
> discussing this topic, we would also like to invite you to
> #openpgp-interop on libera.chat [3].
>
> Best,
> David and Levente
>
> P.S.: The addressed persons have been gathered via links to downstream
> source data on repology.org [4]. In case we have missed anyone (very
> likely), that should join the discussion, please feel free to forward
> this e-mail to them.
>
> [1] https://lists.gnupg.org/pipermail/gnupg-devel/2022-December/035183.html
> [2] https://lists.gnupg.org/pipermail/gnupg-devel/2023-February/035270.html
> [3] ircs://irc.libera.chat/openpgp-interop
> [4] https://repology.org/project/gnupg/versions
>
> --
> https://archlinux.org
[-- Attachment #1.2: Type: text/html, Size: 4788 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next parent reply other threads:[~2023-02-06 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y+FiAeD5eiuC0tMX@hmbx>
2023-02-06 20:27 ` Sam James [this message]
2023-02-07 6:37 ` Fwd: OpenPGP interoperability issues with gnupg >= 2.4 Anna (cybertailor) Vyalkova
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F30D6590-3E0C-4865-A944-7DE118A619CF@gentoo.org \
--to=sam@gentoo.org \
--cc=distributions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).