FS#53949 - [gnupg] Upstream bug affecting all versions after 2.1.16-2

Attached to Project: Arch Linux
Opened by Andrea Chiavazza (ndr76) - Saturday, 06 May 2017, 17:26 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 29 August 2017, 22:15 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

The command "gpg --recv-key <key>" fails with the following error:
gpg: keyserver receive failed: Server indicated a failure

The last package version working fine is 2.1.16-2.
All following versions including 2.1.20-2 are affected by the bug.

I'm still looking for an existing bug report before creating a new upstream bug report.

Steps to reproduce:

After switching to a different version of gnupg, it is necessary to run the command "killall dirmngr".
Remove the key if already exists:
gpg --delete-keys 647F28654894E3BD457199BE38DBBDC86092693E

Run the command:
gpg --recv-key 647F28654894E3BD457199BE38DBBDC86092693E

Expected output:
gpg: key 38DBBDC86092693E: public key "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" imported
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 2 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 2 signed: 0 trust: 0-, 0q, 0n, 0m, 2f, 0u
gpg: next trustdb check due at 2019-02-14
gpg: Total number processed: 1
gpg: imported: 1

Output on versions affected by the bug:
gpg: keyserver receive failed: Server indicated a failure
This task depends upon

Closed by  Gaetan Bisson (vesath)
Tuesday, 29 August 2017, 22:15 GMT
Reason for closing:  Upstream
Comment by Gaetan Bisson (vesath) - Tuesday, 16 May 2017, 18:07 GMT
Please test whether you still experience this bug with gnupg-2.1.21-1 from [testing] using a fresh keyring. If you do, please report this issue upstream.
Comment by Andrea Chiavazza (ndr76) - Tuesday, 16 May 2017, 18:53 GMT
gnupg-2.1.21-1 is still affected by the bug unfortunately.
I tested with a newly created .gnupg directory and after having killed dirmngr.
I will report the issue upstream.
Comment by Andrea Chiavazza (ndr76) - Tuesday, 16 May 2017, 19:25 GMT
Raised bug upstream: https://dev.gnupg.org/T3168

Loading...