[arch-general] mutt and gnupg
jasonwryan at gmail.com
Mon Dec 22 21:44:35 UTC 2014
On 22/12/14 at 02:27pm, Leonid Isaev wrote:
>On Sun, Dec 07, 2014 at 10:45:45AM +1300, Jason Ryan wrote:
>> Yes, but you do need to move to GPGME (or at least that was the only way I
>> restored that functionality).
>Why? Where is it written?
>>(or at least that was the only way I restored that functionality)
>> Update your gpg configuration in your mutt files:
>> set crypt_use_gpgme = yes
>This variable can certainly be set. However, by itself it doesn't do anything
>to help mutt discover the running gpg-agent.
>> Then in your shell profile file, set a couple of variables:
>> export GPG_TTY=$(tty)
>> export GPG_AGENT_INFO=$HOME/.gnupg/S.gpg-agent
>This is also unnecessary. The first variable should anyway be set in the
>.bashrc (or similar). The 2nd one is not needed to be exported globally.
>The real solution would be for mutt to look for gpg-agent sockets. Currently,
>mutt just seems to check GPG_AGENT_INFO in env and ask for a passwd if it is
>It follows that the simplest workaround is to change mutt invocation as
>$ env | grep GPG
>$ GPG_AGENT_INFO="" mutt
>and leave muttrc alone.
So, we only disagree about the content of the variable; ie., it *has* to exist,
but it doesn't matter what is in it, or even if it is empty…
http://jasonwryan.com/ [GnuPG Key: B1BD4E40]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 473 bytes
Desc: not available
More information about the arch-general