diff options
| author | Vincent Breitmoser <look@my.amazin.horse> | 2023-10-21 16:02:47 +0200 |
|---|---|---|
| committer | Vincent Breitmoser <look@my.amazin.horse> | 2023-10-23 14:44:44 +0200 |
| commit | b8f8c9b4139977c197fb7c1c1a7a20a90b88661f (patch) | |
| tree | f7b308f92b5ce485347e52a43c9d339ce8ab9690 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 5542db35fa99606689c0f3d46f7c835809f00f24 (diff) | |
gnupg: revert defaults to openpgp in 2.4 branch
GnuPG upstream changed some of its behavior on the 2.4 branch to use its
own, non-standardized format for keys and encrypted data by default.
This affects in particular the way that keys are generated, and
algorithm capability flags within now signal the ability to use GnuPG's
own AEAD encryption format.
Notably, these formats are not compatible with other implementations of
OpenPGP. It is based on a draft spec that is specific to GnuPG
(draft-koch-openpgp-2015-rfc4880bis), and not compatible with the format
that is on track to be standardized as upcoming OpenPGP version 6.
The political circumstances that led to this issue are complex (and a
bit dumb), but in the end GnuPG emitting incompatible packets is
certainly in noone's interest. This patch is a revert of a GnuPG
upstream commit as it is applied by Fedora, I suggest we follow suit
until the situation becomes more clear.
See also: https://src.fedoraproject.org/rpms/gnupg2/pull-request/15
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions