Gpg (GnuPG) 2.2.9 versus gpg (GnuPG) 1.4.23
Anna Kitces and Seth Fishman
fishkits at hotmail.com
Fri Aug 17 15:59:51 CEST 2018
Dear gpg users:
I am migrating to gpg 2.2
All my gpg 1.4 keys were migrated to 2.2 during the upgrade.
When I try to decrypt a document I am getting the following:
gpg: encrypted with 2048-bit RSA key, ID 2BDB2DD8782B904E, created 2017-03-15
"mykey <fishkits at hotmail.com>"
gpg: public key decryption failed: No pinentry
gpg: decryption failed: No secret key
I am thinking maybe there is a minimum version of pinentry required?
I am running on two platforms: Linux, RHEL 7.3 (Maipo) and Unix, Solaris 11. The Solaris machine has pinentry 0.7.6 already provided and the Linux box has 0.8.1. Is that the reason I am having this issue?
I have tried to upgrade pinentry going through the ./configure, gmake, gmake check, gmake install2 steps but I keep getting errors. So if I must upgrade pinentry, then if anyone has some pointers on this for either of both of these platforms, I'd be most appreciative.
Also, pinentry was not a factor before. Can I just get pinentry out of the equation altogether somehow or is that a bad idea.
Sorry for so many questions. Would appreciate any insight you can provide.
Regards,
Seth Fishman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180817/1e42abb8/attachment.html>
More information about the Gnupg-users
mailing list