Tickets :: [#14780] Horde Cryptography API self-test cannot pass with gpg2

Summary	Horde Cryptography API self-test cannot pass with gpg2
Queue	Horde Framework Packages
Type	Bug
State	Assigned
Priority	1. Low
Owners	Horde Developers (at)
Requester	nish.aravamudan (at) canonical (dot) com
Created	02/05/2018 (2825 days ago)
Due	03/01/2018 (2801 days ago)
Updated	11/23/2020 (1803 days ago)
Assigned	03/02/2018 (2800 days ago)
Resolved
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/23/2020 11:02:16 AM	mike (dot) gabriel (at) das-netzwerkteam (dot) de	Comment #3 New Attachment: 0001-Horde_Crypt_Pgp_Backend-Fix-generateKey-method-with-.patch	Reply to this comment
I stumbled over this issue in Debian unstable (while trying to get the unit tests working again). I send a PR to fix this bug: https://github.com/horde/Crypt/pull/2 The patch is also attached to this bug report now.

03/02/2018 04:39:11 PM	Jan Schneider	Comment #2 Assigned to Horde Developers State ⇒ Assigned	Reply to this comment
See ~~ticket #14664~~ too.

02/05/2018 10:30:57 PM	nish (dot) aravamudan (at) canonical (dot) com	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Framework Packages Due ⇒ 03/01/2018 Summary ⇒ Horde Cryptography API self-test cannot pass with gpg2 Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
generateKey as at https://github.com/horde/Crypt/blob/master/lib/Horde/Crypt/Pgp/Backend/Binary.php#L112 is fundamentally broken with gpg2, where direct interaction with secret keys is no longer possible. In particular, an ignored option (secret_keyring) is passed to --gen-key and then used as if it was not ignored. All secret keys are stored in GNUPGHOME/private-keys-v1.d/ now (and are not named in a way that is trivial to deduce). This blocks the ability for Ubuntu 18.04 to ship an updated php-horde-crypt.