[#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
Requester nish.aravamudan@canonical.com
Created 2018-02-05 (1353 days ago)
Due 03/01/2018 (1329 days ago)
Updated 2020-11-23 (331 days ago)
Assigned 2018-03-02 (1328 days ago)
Resolved
Milestone
Patch No

Comments
nish.aravamudan@canonical.com 2018-02-05 22:30:57
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.

Jan Schneider <jan@horde.org> 2018-03-02 16:39:11
See ticket #14664 too.

mike.gabriel@das-netzwerkteam.de 2020-11-23 11:02:16
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.