On Friday 09 January 2009 07:02:52 Werner Koch wrote: > On Fri, 9 Jan 2009 00:37, cpoll...@embarqmail.com said: > > What would cause this to be displayed in the log? My secret key has been > > imported and I can sign messages. After signing a message this error > > disappears. Any idea what is causing this? > > There is a gpg-agent command HAVEKEY which is used to check whether an > X.509 key is available. The error message may come from there. > > Or if you try to decrypt or sign an CMS message without having > information on the key used. > > Thus this all pertains to X.509/CMS and thus to gpgsm. It might be > possible that you see this if you use --enable-ssh-support. OpenPGP > (gpg2) should not use the agent in this way. To further check you should > look back in the log for the actual command send to the agent. This > will be a line with "gpg-agent[31643.6]" in it. The first number in > brackets is the PID of the agent and the second one the file descriptor > of the connection. > > > Salam-Shalom, > > Werner Thank you for the reply Werner, the error seems to have gone away now and it seems to be working correctly. I did notice one error I'd made and that was a failure to import my secret key when setting this new version up though secring.gpg was in my .gnupg folder.
Thanks -- Chris KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
