[#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 2018-02-05 (1402 days ago)
Due 03/01/2018 (1378 days ago)
Updated 2020-11-23 (380 days ago)
Assigned 2018-03-02 (1377 days ago)
Patch No

2020-11-23 11:02:16 mike (dot) gabriel (at) das-netzwerkteam (dot) de Comment #3
New Attachment: 0001-Horde_Crypt_Pgp_Backend-Fix-generateKey-method-with-.patch Download
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:

The patch is also attached to this bug report now.
2018-03-02 16:39:11 Jan Schneider Comment #2
Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
Reply to this comment
See ticket #14664 too.
2018-02-05 22:30:57 nish (dot) aravamudan (at) canonical (dot) com Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ Horde Cryptography API self-test cannot pass with gpg2
Due ⇒ 2018-03-01
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
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 

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.

Saved Queries