gnupg-2.1 -> 2.1 appears to break decryption of saved messages

[David Wolfskill]

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.
> 
> I ran into this.  The trick is to re-import your key-rings into gpg
> after the upgrade:
> 
>     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
> 
> 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
-- 
David H. Wolfskill				david at catwhisker.org
Actions have consequences ... as do inactions.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20150107/6b2b2ff5/attachment.sig>