Hi Vincent,

On Tuesday, 2018-06-26 08:59:06 -0400, Vincent Lefevre wrote:

> On 2018-06-26 10:14:09 +0200, Eike Rathke wrote:
> > On Monday, 2018-06-25 16:39:19 -0400, Vincent Lefevre wrote:
> > 
> > > It seems that a recent change has broken PGP decryption:
> > > I now get a failure from gnupg. No issues with Mutt from
> > > Debian/unstable.
> > 
> > No problem here, using most recent master with gpgme on Debian stretch.
> 
> I'm not using gpgme, but it appears that Debian's default config
> uses it, so that may be the difference. In short, when gpgme is
> not used, PGP decryption got recently broken.

Still not here.. ;-)
I forced set crypt_use_gpgme=no in my muttrc and decrypt works, verified
that crypt-gpgme.c decrypt_part() is not called.

The gpg.rc pgp_decrypt_command I use is almost the same as distributed
with stretch, just the gpg command renamed to ggp2 (which I needed for
another machine) which nowadays is a symbolic link to /usr/bin/gpg
anyway.

  Eike

-- 
OpenPGP/GnuPG encrypted mail preferred in all private communication.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
Care about Free Software, support the FSFE https://fsfe.org/support/?erack
Use LibreOffice! https://www.libreoffice.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to