[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-devel
Subject:    Re: gpg: error getting the KEK: Unsupported certificate
From:       Werner Koch <wk () gnupg ! org>
Date:       2013-02-09 12:06:50
Message-ID: 87txplzo6d.fsf () vigenere ! g10code ! de
[Download RAW message or body]

On Fri,  8 Feb 2013 16:33, gniibe@fsij.org said:

> "Unsupported certificate" is common error behavior when you are
> using gnome-keyring as gpg-agent.  It replies "103 unknow command",

FWIW, I had a meeting with Stef Walter at FOSDEM and we agreed on a plan
how to solve the gnome-keyring problem.

> 	$ unset GPG_AGENT_INFO
> 	$ eval `gpg-agent  -v --daemon`
> 	$ gpg2 --import secret-keys.gpg

IMHO the best way to test gpg is this

  $ GNUPGHOME=/foo/testdir gpg-agent --verbose --daemon bash

Now within this new shell (bash or whatever you used) you can run your
tests nicely without wondering about GPG_AGENT_INFO etc.  If you want to
terminate the test just enter exit and wait a few seconds until
gpg-agent has terminated itself.  Running watchgnupg in another xterm is
also useful to see what is going on.

If you want to test smartcards you should have put "disable-scdaemon"
into ~/.gnupg/gpg-agent.conf so that the production gpg-agent does not
block the use of the reader device.


Salam-Shalom,

   Werner


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


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
[prev in list] [next in list] [prev in thread] [next in thread]