Skip to content

Handle versions of GnuPG 2.2.x that report the RENC key usage flag#14

Open
dkg wants to merge 1 commit intobestpractical:masterfrom
dkg:handle-renc-2.2
Open

Handle versions of GnuPG 2.2.x that report the RENC key usage flag#14
dkg wants to merge 1 commit intobestpractical:masterfrom
dkg:handle-renc-2.2

Conversation

@dkg
Copy link
Copy Markdown
Contributor

@dkg dkg commented May 24, 2024

GnuPG Upstream has apparently backported work on the putative "RENC" flag to the 2.2.x branch, i think as of 2.2.42.

This means that the output of key listings that have this flag set will change. That breaks the fairly britle parser we have here.

GnuPG Upstream has apparently backported work on the putative "RENC"
flag to the 2.2.x branch, i think as of 2.2.42.

This means that the output of key listings that have this flag set
will change.  That breaks the fairly britle parser we have here.
@gregoa
Copy link
Copy Markdown

gregoa commented Sep 29, 2024

This fails with 2.2.44, cf. https://bugs.debian.org/1082979

@dkg
Copy link
Copy Markdown
Contributor Author

dkg commented Mar 14, 2025

2.4.6 also stopped emitting this r flag, which makes me think that it was a bug all along, and upstream simply has several released versions that fail in this way. In debian, we're just avoiding a failure in the GnuPG::Interface test suite by marking the affected versions and expecting them to emit a bogus r. I can update this MR if there is interest upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants