Bug #12068
The "GnuPG uses the configured keyserver" step needs to be adjusted for Stretch
Start date:
2016-12-23
Due date:
% Done:
100%
Description
We now use GnuPG v2, so network operations are delegated to dirmngr and gpg’s stderr does not mention the keyserver being used.
We should instead parse the output of gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye
(or similar).
And then, perhaps the ugly gnupg_recv_key_res
variable can go away :)
Meanwhile, I’m going to disable this step.
Subtasks
Related issues
Related to Tails - |
Resolved | 2017-01-31 | |
Related to Tails - |
Resolved | 2017-02-03 |
History
#1 Updated by intrigeri 2017-01-31 15:30:26
- related to
Bug #12202: GnuPG can't talk to keyservers on Stretch added
#2 Updated by anonym 2017-02-04 15:13:59
- Status changed from Confirmed to Fix committed
- % Done changed from 0 to 100
Applied in changeset commit:46f9f0c0573f7324363bf8e88646a6a2557ebfcd.
#3 Updated by intrigeri 2017-03-17 09:01:37
- related to
Bug #12211: Adapt GnuPG automated tests after switching to an Onion keyserver added
#4 Updated by intrigeri 2017-04-20 06:27:41
- Status changed from Fix committed to Resolved