-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
From: S3 Subject: pinentry stdin problems
I recently upgraded from GPG v1.4 to GPG v2. Previously, I was able to do this: tar c | gpg -s > a.tar.gpg However, with the new version that uses pinentry, it does not allow me to insert my password whenever I redirect stdin as above. I don't even get the ncurses password entry box. Is there a way to make this work as before? Can pinentry be made to fallback to the plain text password entry, should the other ones fail?
I noticed a (slightly) similar thing when moving from gpg to gpg2, but I happened to be going in the other direction. Here's a small bit of text that was encrypted with gpg2 --armour - --symmetric. The passphrase is "gpg". - -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.8 (Darwin) jA0EAgMCwmLYzXKpwBxgySkGIGW4LYjxGKTNBJDIslO1M0GLMlbjW9ZqJk2HZis7 wqsB2DBwAHpVZw== =juzP - -----END PGP MESSAGE----- With gpg 1.4.8, one could select the text starting with the "BEGIN" line, ending with the "END" line, and paste it as stdin to "gpg - --decrypt". gpg would ask for the passphrase, then decrypt the message. If you try to do the same thing with "gpg2 --decrypt", pinentry-curses winds up getting "-----END PGP MESSAGE-----" as the passphrase. (In my case, the workaround is "don't select the END line". I'm not sure about yours, though). Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (Darwin) iEYEARECAAYFAke7jj4ACgkQX7YJI4BuyDStLQCfVRnC2wUQL42VpH3TNA0WZ2FF evcAnjNNN8jRHI/Ej4BMEHFaEapLkUpj =XaHo -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
