From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnupg: update to 2.4.4
Date: Mon, 29 Jan 2024 18:24:04 +0100 [thread overview]
Message-ID: <20240129172404.D7E8125494@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48419@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/48419#issuecomment-1915216796
Comment:
Even if it's just a version bump, don't merge this without checking extensively what they changed upstream.
```
-----BEGIN ALLEGATIONS-----
```
GnuPG has allegedly made changes in the past that were inconsistent with the OpenPGP standard in a way that deliberately breaks interoperability with other OpenPGP implementations with the alleged goal of weaponizing they userbase against other implementations to get their way with how the standard is supposed to develop in the future.
```
-----END ALLEGATIONS-----
```
We're patching out changes like that already, and we need to be careful with updates to make sure we don't accidentally include updates like that without patching out the unwanted stuff. This is done consistently with other distros as well, with at least Alpine, Arch, Fedora and NixOS shipping a patched version like this. I'm not sure who else also patches GnuPG, but there's going to be a few more I suspect.
next prev parent reply other threads:[~2024-01-29 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 14:57 [PR PATCH] " filiprojek
2024-01-29 15:02 ` [PR PATCH] [Updated] " filiprojek
2024-01-29 17:24 ` jcgruenhage [this message]
2024-01-30 11:02 ` filiprojek
2024-02-01 7:29 ` realcharmer
2024-05-02 1:46 ` github-actions
2024-05-16 1:46 ` [PR PATCH] [Closed]: " github-actions
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=20240129172404.D7E8125494@inbox.vuxu.org \
--to=jcgruenhage@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).