Cannot open *.asc files with gpg -- because no pinentry
When I try to do so I receive the following message:
[GNUPG:] ENC_TO 091EE1D5633F19F2 16 0
[GNUPG:] KEY_CONSIDERED 7D605C8CDA5240843A6B9A8394D949CCE9099937 0
[GNUPG:] KEY_CONSIDERED 7D605C8CDA5240843A6B9A8394D949CCE9099937 0
gpg: encrypted with 4096-bit ELG key, ID 091EE1D5633F19F2, created
2007-12-05
"KenHeard (swimmerken) <ken@heard.name>"
gpg: public key decryption failed: No pinentry
[GNUPG:] ERROR pkdecrypt_failed 67108949
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] DECRYPTION_FAILED
gpg: decryption failed: No secret key
[GNUPG:] END_DECRYPTION
After an internet search I found one responder who suggested that 'the
issue might be in the configuration of your gpg-agent'. So I checked
the contents of the gpg-agent.conf file. There were only two lines:
default-cache-ttl 300
max-cache-ttl 999999
At this point I ran command gpg-agent which returned 'gpg-agent running
and available'.
Another responder said that running the following two commands worked
for him:
pkill gpg-agent
gpg-agent --pinentry-program=/usr/bin/pinentry-gtk-2 --daemon
Before running those two commands I found that I had the following
pinentries:
/etc/alternatives/pinentry*
/usr/bin/pinentry-curses*
/usr/bin/pinentry-tgt*
/etc/alternatives/pinentry-x11*
I then ran those two commands twice, for -curses and -tgt. It may have
worked for him but did not for me.
I finally tried to add to the gpg-agent.conf file the second of those
two commands, also twice, but before trying to decrypt an *anc file I
ran file pkill gpg-agent. That arrangement did not work either. By now
I had run out of suggestions.
I would consequently appreciate any advice as to how to decrypt my *.anc
files.
By the way, I was able to run from an Xterm in succession the commands
gpg -k and -K, which -- without the use of any passkey -- returned
information about my public and secret keys in succession.
Other maybe useful information: I am using Bullseye and had added to my
file .bashrc the following two lines:
GPG_TTY=$(tty)
export GPG_TTY
Reply to: