Debian Bug report logs - #780730
mutt: Does not work correctly with newer gpg-agent

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Guillem Jover <guillem@debian.org>

To: submit@bugs.debian.org

Subject: mutt: Does not work correctly with newer gpg-agent

Date: Wed, 18 Mar 2015 14:14:33 +0100

[Message part 1 (text/plain, inline)]

Package: mutt
Version: 1.5.23-3
Severity: wishlist
Tags: patch

Hi!

With recent GnuPG versions, the gpg-agent is always used, and is
started on demand if not already running. It also now uses a stable
socket pathname and as such does not need (and actually ignores) the
GPG_AGENT_INFO environment variable.

I had prepared a patch that uses that socket address also to determine
if the agent is running, but that's actually wrong, because not having
the agent running is a valid configuration and gpg2 will take care of
starting it if needed. So the only sane option with newer gpg2 is to
ignore the environment varialbe altogether. This can cause issues for
people using older gpg, but I'd say that if they are setting
pgp_use_gpg_agent=yes then they should know what they are doing?

In any case I'm attaching both patches, but the correct one to use
is the one that removes the check for the environment variable
(gpg2-agent-always.patch).

Thanks,
Guillem

[gpg2-agent-always.patch (text/x-diff, attachment)]

[gpg2-agent-socket.patch (text/x-diff, attachment)]

Message #10 received at 780730@bugs.debian.org (full text, mbox, reply):

From: "Kevin J. McCarthy" <kevin@8t8.us>

To: 780730@bugs.debian.org

Subject: mutt: Does not work correctly with newer gpg-agent

Date: Sat, 11 Apr 2015 14:19:31 -0700

Also note that http://dev.mutt.org/hg/mutt/rev/df55f14f4585 committed
upstream removes the agent check.

-Kevin

Message #21 received at 780730-done@bugs.debian.org (full text, mbox, reply):

From: Antonio Radici <antonio@dyne.org>

To: 780730-done@bugs.debian.org

Subject: Re: mutt: Does not work correctly with newer gpg-agent

Date: Mon, 15 Feb 2016 21:34:22 +0000

Fixed in 1.5.24-1, thanks Kevin

Send a report that this bug log contains spam.