On Fri, Dec 05, 2014 at 09:55:22AM -0600, Troy Engel wrote:

On Fri, Dec 5, 2014 at 3:53 AM, Magnus Therning wrote:

...

So, is there some way to configure mutt to go straight to the gpg-agent, without any warning messages on startup?

I fought with this as soon as it came out and engaged upstream - v2.1.x requires the agent and pinentry, you'll need to work out a change in your configuration to use "loopback" mode in pinentry. Based on the forum thread and upstream bug report I worked out these instructions for a general case:

https://wiki.archlinux.org/index.php/Gnupg#Unattended_passphrase

If you figure out another case that is needed, please update the wiki with your new find. :)

Hmm, that configuration basically makes GnuPG *not* use the pinentry program and makes mutt completely bypass the use of gpg-agent. I rather like gpg-agent and the pinentry program... so I'd much rather configure mutt to work with standard behaviour of v2.1.x. Is that possible? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay

On Sun, Dec 07, 2014 at 10:45:45AM +1300, Jason Ryan wrote:

On 06/12/14 at 10:36pm, Magnus Therning wrote:

...

On Fri, Dec 05, 2014 at 09:55:22AM -0600, Troy Engel wrote:

...

On Fri, Dec 5, 2014 at 3:53 AM, Magnus Therning wrote:

...

So, is there some way to configure mutt to go straight to the gpg-agent, without any warning messages on startup?

I fought with this as soon as it came out and engaged upstream - v2.1.x requires the agent and pinentry, you'll need to work out a change in your configuration to use "loopback" mode in pinentry. Based on the forum thread and upstream bug report I worked out these instructions for a general case:

https://wiki.archlinux.org/index.php/Gnupg#Unattended_passphrase

If you figure out another case that is needed, please update the wiki with your new find. :)

Hmm, that configuration basically makes GnuPG *not* use the pinentry program and makes mutt completely bypass the use of gpg-agent.

I rather like gpg-agent and the pinentry program... so I'd much rather configure mutt to work with standard behaviour of v2.1.x. Is that possible?

Yes, but you do need to move to GPGME (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

Then in your shell profile file, set a couple of variables: export GPG_TTY=$(tty) export GPG_AGENT_INFO=$HOME/.gnupg/S.gpg-agent

Now you will get the pinentry prompt in mutt, and your gpg-agent will continue to work for other services (which the loopback hack breaks, as noted in the GPG release notes).

IIRC those used to *have* to be set, and that was done via the loginmanager (e.g. gdm), but that doesn't seem to be necessary any longer, but I guess mutt depends on them being there in order to find out that gpg-agent is running. Is that correct? Anyway, making the changes you propose makes mutt behave the way I want. Thanks! /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Code as if whoever maintains your program is a violent psychopath who knows where you live. -- Anonymous

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 not set.

It follows that the simplest workaround is to change mutt invocation as ------ $ env | grep GPG GPG_TTY=/dev/pts/4 $ 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… /J -- http://jasonwryan.com/ [GnuPG Key: B1BD4E40]