Date: Wed, 7 Jan 2015 11:27:42 -0800 From: David Wolfskill <david@catwhisker.org> To: freebsd-ports@freebsd.org Subject: Re: gnupg-2.1 -> 2.1 appears to break decryption of saved messages Message-ID: <20150107192742.GK14822@albert.catwhisker.org> In-Reply-To: <54AD6E3B.5000005@FreeBSD.org> References: <20141120192552.GJ31571@albert.catwhisker.org> <20150107134934.GA75522@dohhoghi.mutt.home.crhalpin.org> <20150107151612.GE14822@albert.catwhisker.org> <54AD6E3B.5000005@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--SLAil/ztx45+OLrp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 07, 2015 at 05:34:51PM +0000, Matthew Seaman wrote: > ... > >> 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 . > ... > > Unfortunately, that wasn't my experience. I'll revert back to gnupg-2.0 > > for now. >=20 > I ran into this. The trick is to re-import your key-rings into gpg > after the upgrade: >=20 > cd ~/.gnupg > mv pubring.gpg pubring-210.gpg > mv secring.gpg secring-210.gpg > mv trustdb.gpg trustdb-210.gpg > gpg --import pubring-210.gpg > gpg --import secring-210.gpg (Prompts for passphrases) > rm pubring-210.gpg > rm secring-210.gpg > mv trustdb-210.gpg trustdb.gpg >=20 > Then you should be able to do 'gpg --list-secret-keys' and similar, and > mutt should work properly again. > ... OK; I finally had some time to try this. * I ran "portmaster -o security/gnupg{,20}" to replace security/gnupg20 with security/gnupg. * I performed the above setps (except for the "rm" ones). * I attempted to use mutt to read a locally-stored encrypted messgae. That attempt failed is the (now) usual way. * I performed the steps suggested by Corey Halpin(re. the "loopback" pinentry mode). * I re-tried using mutt to read the encrypted message; it still failed for me in the same way. * I ran "portmaster -o security/gnupg{20,}" to revert to security/gnupg20. * I re-tried using mutt to read the encrypted message; it still failed for me in the same way. * In ~/.gnupg, I moved aside the new *.gpg files and moved my old ones into place. * I re-tried using mutt to read the encrypted message; it still failed for me in the same way. * I reverted the "loopback" mode pinentry specifications in ~/.muttrc. * I re-tried using mutt to read the encrypted message; it worked. Ugh. :-( Peace, david --=20 David H. Wolfskill david@catwhisker.org Actions have consequences ... as do inactions. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --SLAil/ztx45+OLrp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUrYitXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7jv0QAJhV08Bf5L15P8I1kmcto046 RMnE02Pr6hLtFTKvP1/9/8mlDpXe+88GIYpogGxlb7HtL2JT9NvHBlLJ205f9hse GtZgTlCEUemWDMs4Ly7/VNpXBgAxlb/5wXA2e4O2pzPzL4tTB+1GvfMKfx0mI4Go O0aftBCDw3mhVitU0DreWjEYzi8smj07JklStV+v5i83cW9trY/UxfxbPWKB0SJl qDE7ZUJNyE3SyUrzd82rcH1Ib44tLMMPNzg1ztCleGXaTs61/a4NqPt2ivzAWttl NNedgkDJJxd+OCLZfgjulSTk50QCUhO2GVzky8N1L3xaBh43z5tLYMHUJxY27UPC H3GH51g5E+W3eD59Ri8bzIJFnRMtWdNMNx/MTHx8KvITWIgz8WEwieXQtoza0o+v bZKH7Z1xt+qlWL/D0IBt+OSeMv/ejyXM620g2b3Jl9YHorc6GVtgqzHNXT4izXBQ Yrt/1puyFsRz5WxJFVVevqmZ+M2O+2WH+GEhgm5hL61ysJ5P1LA7gs8QbLbM2Wc7 n5EM/+wYGMS83yVdl3WgLIVhZL16yVXJs6I3v/Nl4VBoEwhjR5elWLqHx0mihf/Q 57KEJX/522Nlm5LUh/wG0ETCzdNF1RMoKjSz/52xngzQviOFYzgkVZ5Md0mI77Ub slNMTUWr8gFEZCv9Y8n1 =kJbW -----END PGP SIGNATURE----- --SLAil/ztx45+OLrp--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150107192742.GK14822>