Marco d'Itri wrote: > On Jun 30, Joey Hess <[EMAIL PROTECTED]> wrote: > > > I'm not using gpgme, so the first line is the one that's a problem. > > gpg-agent 1.9.15-6 does not set a GPG_TTY variable. I tried setting > > this variable and mutt began using the agent properly. > I understand that this is a feature. Feel free to argue against it with > the upstream developers.
Maybe the mutt developers are not up to speed with the current versions of gnupg and pinentry in Debian, neither of which need GPG_TTY. GPG_TTY was only ever useful if you wanted to use a curses based pinentry. Mutt has no business knowing or caring what kind of pinentry I'm using, or even if I'm using one at all. Perhaps I am presetting the passphrase in gpg-agent. Anyway, current versions of gpg and pinentry work perfectly well, even at the console, without GPG_TTY being set. gpg falls back to using ttyname() and other methods to get the tty to pass to pinentry. BTW I think it's illuminating that most hits for GPG_TTY are about how to get mutt to work properly. -- see shy jo
signature.asc
Description: Digital signature
