On Tue, 19 Aug 2008 12:01, [EMAIL PROTECTED] said: > Do anyone have any suggestions on how to proceed?
Check out whether scdaemon is working, example: $ gpg-connect-agent > scd serialno S SERIALNO D2760001240101010001000003470000 0 OK > Youy probably get an error here. To further investigate this, you first need to see whether scdaemon has been started (by gpg-agent). If that is the case, you add log-file /tmp/foo/scd.log debug-ccid-driver debug 2028 debug 1024 to ~/.gnupg/scdaemon.conf and kill scdaemon (check that it is really killed, usually it required two sigints). The log file will give you an idea on what scdaemon is doing. Take care, the debug options may reveals PINs. You can also add this to gpg-agent.conf: log-file /tmp/foo/agent.log debug 1024 and give gpg-agent a HUP. To see everything compined in one log, use log-file socket:///foo/bar/S.gnupg-log instead of the file name and run watchgnupg --force /foo/bar/S.gnupg-log in another xterm. Shalom-Salam, Werner -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
