Contents
Why is there no secret key in GPG?
1. This message can also happen if your key is protected with a passphrase, and your pinentry program isn’t working properly. In this case, gpg can’t get the passphrase to unlock the decryption key. If this is the case, gpg –list-keys will show the correct key, but gpg -d -v will appear to select the correct key and then just hang
Why is GPG not able to decrypt a message?
Ask for the private key if you are required to decrypt the message, or ask the sender to encrypt using symmetric cryptography and share the passphrase with you. This message can also happen if your pinentry program isn’t working properly, and thus gpg can’t get the passphrase to unlock the decryption key. This has happened to me a couple of times.
Why is my GPG not getting the passphrase?
This message can also happen if your pinentry program isn’t working properly, and thus gpg can’t get the passphrase to unlock the decryption key. This has happened to me a couple of times.
How to decrypt GnuPG GPG on OS X?
The steps depend on your specific environment, but checking (or creating) the pinentry-program option in ~/.gnupg/gpg-agent.conf is a good place to start. In my case (on OS X with Homebrew-installed gpg and pinentry-mac) I had to create that file with the following contents:
Why does GPG-D-V say decryption failed?
This message can also happen if your pinentry program isn’t working properly, and thus gpg can’t get the passphrase to unlock the decryption key. This has happened to me a couple of times. If this is the case, gpg -d -v will appear to select the correct key and then just hang for a while before giving up.
What happens if GPG can’t get the passphrase?
In this case, gpg can’t get the passphrase to unlock the decryption key. If this is the case, gpg –list-keys will show the correct key, but gpg -d -v will appear to select the correct key and then just hang for a while before giving up. This is it waiting for the pinentry that never actually returns.
How to check git config for gpg2?
Check first the git config gpg.program to see if this is gpg or gpg2 (as in here ). And type where gpg nd where gpg2 to check which path is considered for the GPG program. That should force Git/GPG to act as gpg2.