Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.6.9
Bug #21016 Signing is broken for gnupg 2.0.28
Submitted: 2016-01-07 23:33 UTC
From: internethering Assigned: alec
Status: Closed Package: Crypt_GPG (version 1.4.0)
PHP Version: 5.6.16 OS: Gentoo Linux
Roadmaps: 1.4.1    
Subscription  


 [2016-01-07 23:33 UTC] internethering (Richard Hering)
Description: ------------ Hi, I'm using roundcube 1.2-beta with enigma-plugin (http://bit.ly/1OSnYDj). When I try to sign, it failes with gnupg 2.0.28 but works with gnupg 2.0.26 - so I think, its a problem between gnupg and crypt_gpg I attached the debug-log of both versions.

Comments

 [2016-01-07 23:34 UTC] internethering (Richard Hering)
GNUPG 2.0.28 [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: /usr/bin/gpg --status-fd '3' --command-fd '4' --no-secmem-warning --no-tty --no-default-keyring --no-options --no-permission-warning --exit-on-status-write-error --trust-model always --armor --textmode --local-user '2C193C1CFCD3B32F30E860531B108E8A2BDF7FD4' --homedir '/var/www/v10003/docroot/enigma/richard@richardhering.de' --clearsign [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: BEGIN PROCESSING [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: GPG is ready for input [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => about to write 4 bytes to GPG input [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => wrote 4 bytes [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: GPG status stream ready for reading [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG status [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => read 143 bytes [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: STATUS: USERID_HINT 1B108E8A2BDF7FD4 Richard Hering <richard@richardhering.de> [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: STATUS: NEED_PASSPHRASE 1B108E8A2BDF7FD4 1B108E8A2BDF7FD4 1 0 [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: GPG is ready for command data [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => about to write 16 bytes to GPG command [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => wrote 16 [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:11:50 Europe/Berlin] Crypt_GPG DEBUG: selecting streams GNUPG 2.0.26 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: /usr/bin/gpg --status-fd '3' --command-fd '4' --no-secmem-warning --no-tty --no-default-keyring --no-options --no-permission-warning --exit-on-status-write-error --trust-model always --armor --textmode --local-user '2C193C1CFCD3B32F30E860531B108E8A2BDF7FD4' --homedir '/var/www/v10003/docroot/enigma/richard@richardhering.de' --clearsign [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: BEGIN PROCESSING [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG is ready for input [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to write 4 bytes to GPG input [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => wrote 4 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG status stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG status [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 143 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: STATUS: USERID_HINT 1B108E8A2BDF7FD4 Richard Hering <richard@richardhering.de> [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: STATUS: NEED_PASSPHRASE 1B108E8A2BDF7FD4 1B108E8A2BDF7FD4 1 0 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG is ready for command data [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to write 16 bytes to GPG command [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => wrote 16 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG status stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG status [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 51 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: STATUS: GOOD_PASSPHRASE [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: STATUS: BEGIN_SIGNING H2 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => got 1 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG output stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG output [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 52 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => got 2 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG output stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG output [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 819 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG status stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG status [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 82 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: STATUS: SIG_CREATED C 1 2 01 1452208708 2C193C1CFCD3B32F30E860531B108E8A2BDF7FD4 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: selecting streams [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => got 3 [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG output stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG output [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 0 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG error stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG error [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 0 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG status stream ready for reading [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => about to read 8192 bytes from GPG status [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => read 0 bytes [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: => closing GPG input pipe [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: END PROCESSING [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: CLOSING GPG SUBPROCESS [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: STOPPING GPG-AGENT DAEMON [08-Jan-2016 00:18:28 Europe/Berlin] Crypt_GPG DEBUG: GPG-AGENT DAEMON STOPPED
 [2016-01-08 12:16 UTC] alec (Aleksander Machniak)
Is the 2.0.28 log complete? It looks like it just stopped working at some point? Any errors in (Roundcube or http server) log? Did you try to sign a message using gnupg in command line, e.g.: /usr/bin/gpg --no-secmem-warning --no-default-keyring --no-options --no-permission-warning --exit-on-status-write-error --trust-model always --armor --textmode --local-user '2C193C1CFCD3B32F30E860531B108E8A2BDF7FD4' --homedir '/var/www/v10003/docroot/enigma/richard@richardhering.de' --clearsign
 [2016-01-08 16:14 UTC] internethering (Richard Hering)
yes, the log is complete. the request got no response and I have some open processes: v10003 23334 0.4 0.2 481520 42776 ? S 16:13 0:00 php-fpm: pool v10003 v10003 23398 0.0 0.0 14052 2112 ? Ss 16:13 0:00 /usr/bin/gpg-agent --options /dev/null --csh --keep-display --no-grab --ignore-cache-for-signing --pinentry-touch-file /dev/null --disable-scdaemon --no-use-standard-socket --pinentry-program /usr/bin/crypt-gpg-pinent v10003 23399 0.0 0.0 23268 3424 ? SL 16:13 0:00 /usr/bin/gpg --status-fd 3 --command-fd 4 --no-secmem-warning --no-tty --no-default-keyring --no-options --no-permission-warning --exit-on-status-write-error --trust-model always --armor --textmode --local-user 2C193C v10003 23400 0.0 0.1 255112 31620 ? S 16:13 0:00 php /usr/bin/crypt-gpg-pinentry I found nothing else in the logs. On commandline the command is running fine and the difference is: diff 2.0.28.asc 2.0.26.asc 2c2 < Hash: SHA256 --- > Hash: SHA1 ATM I've no idea. The running processes are open since one hour.
 [2016-01-08 16:21 UTC] alec (Aleksander Machniak)
Did you try to run these in command line? php /usr/bin/crypt-gpg-pinentry /usr/bin/gpg-agent --options /dev/null --csh --keep-display --no-grab --ignore-cache-for-signing --pinentry-touch-file /dev/null --disable-scdaemon --no-use-standard-socket --pinentry-program /usr/bin/crypt-gpg-pinentry
 [2016-01-25 12:21 UTC] alec (Aleksander Machniak)
Could you try the patch from https://github.com/pear/Crypt_GPG/pull/18 ?
 [2016-01-27 19:13 UTC] internethering (Richard Hering)
yay, with the Patch everything is working.
 [2016-01-28 10:32 UTC] alec (Aleksander Machniak)
-Status: Open +Status: Closed -Assigned To: +Assigned To: alec
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.