On Tue, 28 Aug 2007 01:24, [EMAIL PROTECTED] said:
> echo '...STARTING GPG-AGENT' > eval `/usr/local/bin/gpg-agent --daemon` > echo $GPG_AGENT_INFO >$HOME/.gpg-agent-info BTW, you can do this easier by using gpg-agent's --write-env-file option. > ~> env | grep GPG > GPG_AGENT_INFO=/tmp/gpg-GqplAN/S.gpg-agent:89498:1 > GPG_TTY=/dev/ttypm Looks good. Two things you should test: 1. Run pinentry manually: $ pinentry GETPIN If this works, pinentry is okay. 2. Get the gpg-connect-agent tool (It is part of gnupg2) $ gpg-connect-agent GET_CONFIRMATION X X X X You should then get a pinentry dialog. If this works. the problem is due to gpg. To debug this, I suggest to use ktrace to tarce the system calls done by gpg. Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
