Date: Wed, 7 Jan 2015 07:49:34 -0600 From: Corey Halpin <chalpin@cs.wisc.edu> To: David Wolfskill <david@catwhisker.org> Cc: freebsd-ports@freebsd.org Subject: Re: gnupg-2.1 -> 2.1 appears to break decryption of saved messages Message-ID: <20150107134934.GA75522@dohhoghi.mutt.home.crhalpin.org> Resent-Message-ID: <20150107145547.GA9149@dohhoghi.mutt.home.crhalpin.org> In-Reply-To: <20141120192552.GJ31571@albert.catwhisker.org> References: <20141120192552.GJ31571@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2014-11-20, David Wolfskill wrote: > It has been my practice for several years to email sensitive information > (such as passwords) to myself via envrypted email, using mutt and GPG. > > [...] > > Then, a few minutes ago, I tried to retrieve a password from one of my > saved encrypted messages... only to be informed "Could not copy > message". I also enjoyed some friction trying to use gnupg 2.1 with mutt, though I didn't get the "Could not copy message" error that you report. Instead I was seeing 'no secret key'. In my case, this was resolved by following the advice at https://wiki.archlinux.org/index.php/GnuPG#Unattended_passphrase . Namely: echo allow-loopback-pinentry >> ~/.gnupg/gpg-agent.conf and editing my copy of mutt's gpg.rc to add '--pinentry-mode loopback' to every gpg invocation involving a passphrase-fd. After that, things were back to normal for me. Hopefully this helps others avoid the same problem. ~crh --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iF4EAREIAAYFAlStOW4ACgkQR8PgTIRJoTW4pgEAsHP5gFhoRiJWz0vcvE6SQIm3 otlFMVpYBUHCseRMBmMA/0MCRzxqTfBA77YQ658zbJ5xS28FyXB1fpUXf0eIxsIt =/UD7 -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150107134934.GA75522>