| Summary | Key generations fails with gpg > 2.1 |
| Queue | IMP |
| Queue Version | 6.2.17 |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | debugs (at) systemausfall (dot) org |
| Created | 06/30/2017 (3039 days ago) |
| Due | |
| Updated | 03/02/2018 (2794 days ago) |
| Assigned | |
| Resolved | 03/02/2018 (2794 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
queue already.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Key generations fails with gpg > 2.1
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
generation fails with the execption "Cannot generate PGP keys"[1].
I think the problem is that gpg2 doesn't create the files secring.pgp
and pubring.pgp any more[2] but Horde expect to find the newly created
key there.
[1]
https://github.com/horde/horde/blob/master/framework/Crypt/lib/Horde/Crypt/Pgp/Backend/Binary.php#L153
[2] https://www.gnupg.org/faq/whats-new-in-2.1.html#nosecring