On 09/11/2016 08:52 PM, Daniel Kahn Gillmor wrote:
> this command should not cause the pinentry to appear; what command are
> you running that actually causes pinentry to appear? what operating
> system are you running? are the gnupg packages supplied by the OS or
> have you built them by hand?
On 09/09/2016 05:55 AM, Stephan Beck wrote:
> AFAIK, this means that the agent is not started when you "invoke gpg2
> normally" (directly from the command line?), so the environment may be
> incorrectly set. Or is there more than one agent instance running?
When gpg2 is called, the agent appears t
Hi Antony--
On Thu 2016-09-08 00:44:34 +0200, Antony Prince wrote:
> I know this has got to be something simple. When invoking gpg2 normally
> to decrypt, I get:
>
> gpg: encrypted with 4096-bit RSA key, ID 0E98CD22ADB13E99, created 2015-05-06
> "Antony Prince "
> gpg: public key decryption
Hi Antony,
just some ideas to (possibly) track it down...
Antony Prince:
> I know this has got to be something simple. When invoking gpg2 normally
> to decrypt, I get:
>
> gpg: encrypted with 4096-bit RSA key, ID 0E98CD22ADB13E99, created
> 2015-05-06
> "Antony Prince "
> gpg: public key d
I know this has got to be something simple. When invoking gpg2 normally
to decrypt, I get:
gpg: encrypted with 4096-bit RSA key, ID 0E98CD22ADB13E99, created
2015-05-06
"Antony Prince "
gpg: public key decryption failed: No pinentry
gpg: decryption failed: No secret key
I have pinentry-prog
