On 2016-10-25 17:40:03 -0400, Daniel Kahn Gillmor wrote: > since each user has a single gpg-agent (thanks to the standard-socket), > I see a few choices here: > > a) use pinentry-emacs where possible (this won't currently work within > debian since none of our pinentry implementations are configured to > support emacs, though this could change) > > b) emacs could use "--pinentry-mode loopback" and directly handle the > user's passphrase > > c) emacs could pass its controlling tty to the gpg process and rely on > pinentry-curses or pinentry-tty (or any comparable fallback > mechanism) to handle the situation. > > I've opened the uptsream bug report > https://bugs.gnupg.org/gnupg/issue2818 to try to track this problem, as > i'm not sure the best way to solve it.
This is not specific to Emacs. There's the same problem with "gpg -d file.gpg" instead of "emacs file.gpg". I suppose that if gpg communicates its $DISPLAY and $GPG_TTY to gpg-agent, gpg-agent should be able to know what to do. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
