Tickets :: Comment on [#14548] php-horde-crypto: needs updating for gpg2 cli changes

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ . ..__ .__. [__)[__)\| \|[ __\| \| \| [__)\|/\\|[_./\|__\|
Comment	> gpg2 (now the default e.g. on Ubuntu), has a different CLI output > format. But the Horde Crypto library relies on parsing that output > for self-verification (and I assume, therefore, for behavior). > > The changes in the attached patch include setting a GPG environment > variable (without which you get a cryptic error message from gpg2) > and then setting some global flags for gpg (--keyid-format short and > (if not v1) --pinentry-mode loopback). > > I also split testVerifyPassphrase into two tests. This is because > gpg2 always spawns a gpg-agent which caches passphrases. So within > one gpg2 session (which each test counts as), the first successful > message decryption (using the correct passphrase) ends up staying > cached and falsely passing the bad passphrase case. Alternatively, > the function could be left as one and the order of the calls could be > changed.
Attachment
Watch this ticket