Arch Linux

degmic71

Member

Registered: 2009-02-03

Posts: 122

gpg / gpgme gave error Pinentry:263: Line passed to IPC too long

I keep getting this error when connecting via SSH to my Arch Linux box. It seems to only happen only over SSH. I have checked https://wiki.archlinux.org/index.php/GnuPG for any hints of why this may be happening. GPG_TTY is set to `/dev/pts/0` while logged in via SSH on my Android device. DISPLAY is not set, but I have never set that before. I was checking around the net and did stumble upon error codes (http://www.gnu-darwin.org/www001/src/po … codes.h.in), noting

# Error codes pertaining to the Assuan IPC interface
263	GPG_ERR_ASS_LINE_TOO_LONG	Line passed to IPC too long

Signing works normally with my main personal key:

gpg --sign test-file

But, a specific key I have used main times in the past gives "gpg: singing failed: Line passed to IPC too long". That error displays twice, which is odd as well. The funny thing is, if I sign a test file with another key, it seems to "unlock" things, and I can then sign a new file with the "bad" key.  This is lost upon reboot. /usr/bin/pinentry-tty works , but not /usr/bin/pinentry-curses

Fix?:

It seems that loopback legacy support is not enabled. This is described in the Arch Linux wiki, (https://wiki.archlinux.org/index.php/GnuPG#pinentry. After I sign a file, `reprepro export` instantly works without a passphrase. Removing 'allow-loopback-entry' from ~/.gnupg/gpg-agent.conf and reloaded with 'gpg-connect-agent reloadagent /bye' allows gpg --sign <KEY> to function again on this particular key. This tells me that gpg/gpg-agent works with loopback enabled, but reprepre will ignore it, unless a file is first signed before 'reprepro exprt' is issued.

Last edited by degmic71 (2016-11-09 20:11:38)