On Sun 2016-12-04 20:37:47 -0500, Ryan Kavanagh wrote: > Guessing from the bug report and from the fact that > ~/.gnupg/.gpg-v21-migrated is empty, the first command was supposed to > be an rm on that file.
whoop, yes, you're right. > rak@zeta:~$ echo "ABC" | gpg -r$GPGKEY1 --encrypt | gpg --debug 8 --decrypt > gpg: reading options from '/home/rak/.gnupg/gpg.conf' > gpg: enabled debug flags: filter > gpg: encrypted with 2048-bit ELG key, ID 6C6FA7C974FCFC3F, created 2006-02-22 > "Ryan Kavanagh (kubuntu.org email alias) <ryana...@kubuntu.org>" > gpg: public key decryption failed: Inappropriate ioctl for device […] > rak@zeta:~$ readlink -f $(which pinentry) > /usr/bin/pinentry-curses […] > rak@zeta:~$ echo "abc" > /tmp/abc && gpg --clearsign /tmp/abc > gpg: using "8F7BF8FC4A11C97A" as default secret key for signing > <I get prompted for my passphrase via pinentry-curses> > rak@zeta:~$ gpg --verify /tmp/abc.asc > gpg: Signature made Sun 04 Dec 2016 08:34:55 PM EST > gpg: using RSA key 4E469519ED677734268FBD958F7BF8FC4A11C97A > <snip> do you have GPG_TTY set? if not, can you retry the first command after having done: GPG_TTY=$(tty) in the failed example, stdin of --decrypt is set to the incoming data stream. in the two successful examples, stdin is just the terminal's attached stdin. if you set GPG_TTY then gpg will tell gpg-agent (which will tell pinentry-curses) which terminal it should prompt on. Upstream tends to recommend setting GPG_TTY in your .bashrc. I will say that this: > gpg: public key decryption failed: Inappropriate ioctl for device > gpg: decryption failed: No secret key Is a very unclear set of error messages to give you a hint that this is the case, though :/ --dkg
signature.asc
Description: PGP signature