On Sat,  9 Sep 2017 14:54, philip.jack...@nordnet.fr said:

> Suggestions as to how to check and correct this situation would be
> appreciated.

Newer versions of gpg should print a better error message; at least with
-v.  I guess that your pinentry is not installed or can't be used.

Do you have the option "pinentry-program" in your gpg-agent.conf ?  Then
check that it is really there.

Is the environment variable GPG_TTY set as describen in the manual?

Do you get a prompt when calling "pinentry"?  If so, does it show up a
window after entering "getpin"?

More information about gpg-agent an pinentry interaction can be seen by
putting

--8<---------------cut here---------------start------------->8---
log-file /somewhere/gpg-agent.log
verbose
debug ipc
debug-pinentry
--8<---------------cut here---------------end--------------->8---

into gpg-agent.conf and restarting gpg-agent ("pkill gpg-agent" or
"gpgconf --kill gpg-agent").


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

Attachment: pgpUA6YozyS7t.pgp
Description: PGP signature

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Reply via email to