On 11 August 2015 at 19:44, Thomas Kahle <[email protected]> wrote: > If somebody knows how to configure pinentry curses correctly (in > particular with respect to screen/multiplexing and long running > sessions, that would be a great help (and wiki addition).
I suspect its more a bug in GPG than pinentry, as it appears to be GPG which tells pinentry which tty to write to. And the GPG-Agent appears to keep trying to attach to the original tty it was spawned in, instead of the one its being queried in. An example of this can be seen if you spawn two local terminals, authenticate GPG in it with pin-entry, and the hide that terminal somewhere for later. Then, when the agent expires and re-prompts you for a pin, your current terminal, instead of getting the "cancelled by user" message, you instead get it blocking indefinitely. Then, you can go hunting for that terminal you originally started and authenticated GPG-Agent in, and you might find its suddenly asking for input. ( Which may or may not actually be usable ). ^ is a hideous and dangerous bug IMHO. The only solution I know is consistently viable is ensuring your tty's you intend to do pin-entries in have GPG_TTY=$(tty) in their environment. -- Kent KENTNL - https://metacpan.org/author/KENTNL
