Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Jul 2018 08:23:13 -0600
From:      Adam Weinberger <adamw@adamw.org>
To:        david@catwhisker.org
Cc:        freebsd-ports@freebsd.org
Subject:   Re: After mutt-1.10.0_1 -> mutt-1.10.1 upgrade, gnupg fails
Message-ID:  <CAP7rwcj9rh-o4Lx4mT0sHuSCQPYELumHV=q8NDgMF36p5qv6-w@mail.gmail.com>
In-Reply-To: <20180720125251.GE12958@albert.catwhisker.org>
References:  <20180720125251.GE12958@albert.catwhisker.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 20, 2018 at 6:53 AM David Wolfskill <david@catwhisker.org> wrote:
>
> This is running:
>
> FreeBSD g1-215.catwhisker.org 11.2-STABLE FreeBSD 11.2-STABLE #685  r336523M/336541:1102501: Fri Jul 20 03:40:05 PDT 2018     root@g1-215.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY  amd64
>
> and after updating all installed ports to reflect the ports "head"
> branch at r475002.
>
> A symptom is that an attempt to send a signed, unencrypted message
> yields a failure, with the messages:
>
> | gpg: skipped "0x6757003D": Unusable secret key
> | gpg: signing failed: Unusable secret key
>
> This works on another machine (the one I'm using to send this
> message), with the same gnupg/mutt setup, but running mutt-1.10.0_1.
>
> I have not configured mutt to use gpgme, though I'm willing to try
> it.  I recall that I needed to tweak ~/.muttrc a bit after the
> gnupg-2.0 -> gnupg-2.1 update -- though that change was merely
> commenting out the 'pgp_verify_command' line.
>
> I note that a result of the mutt upgrade is that
> /usr/local/share/examples/mutt/gpg.rc has changed, but that change
> was merely to remove the pgp_decryption_okay setting (which I don't
> have) and add 'set pgp_check_gpg_decrypt_status_fd'; I tried adding
> that, to no avail.
>
> Any hints or suggestions?
>
> Thanks!
>
> Peace,
> david

Hi, David!

FWIW, I'd highly suggest using gpgme.
  set crypt_use_gpgme=yes
has replaced my entire gnupg command file.

gnupg was just updated to 2.2.9 a few days ago, so that might be the
cause (and not mutt). Are you able to successfully use that key from
the command-line?

# Adam


-- 
Adam Weinberger
adamw@adamw.org
https://www.adamw.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP7rwcj9rh-o4Lx4mT0sHuSCQPYELumHV=q8NDgMF36p5qv6-w>