Mailing List Archive

Marco d'Itri <md@linux.it> writes:

> How can I select the keyring where newly imported keys will go?

What about: the last keyring specified is used. Order is: default
keyrings, keyrings from options, keyrings from the command line.

I have to make sure that this is always guaranteed.


Werner


--
ceterum censeo RSA esse delendam

Hi,

Werner Koch:
> > How can I select the keyring where newly imported keys will go?
>
> What about: the last keyring specified is used. Order is: default
> keyrings, keyrings from options, keyrings from the command line.
>
I'd like to have an option to always add the key to the keyring specified
on the command line, even if it already is on one of the others.

[ Looking through the manpage ] Oh, there is a no-default-keyring option,
how nice -- hmmm, but that only turns off the builtin keyring, not the one
in the options file.

Oh yes, and if I have more than one keyring, how about defaulting to the
ring which has the most signature matches? I.e., I might have a private and
a company keyring in my options file, and when I import the key of our
newest coworker gpg would notice that it's signed by some of the keys on
the company ring, and automatically save it there.

--
Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661
The quote was selected randomly. Really. | http://www.noris.de/~smurf/
--
Zeus gave Leda the bird.

Matthias Urlichs <smurf@noris.de> writes:

> I'd like to have an option to always add the key to the keyring specified
> on the command line, even if it already is on one of the others.

I take this in account.

> Oh yes, and if I have more than one keyring, how about defaulting to the
> ring which has the most signature matches? I.e., I might have a private and

Code for handling different keyrings is extremly ugly and I see no
solution to work with different keyrings in a reasonable manner. It
is simply not possible to work with a 2nd database which can be seen
as a different revision of the first one.

A keyring for the own keys makes sense but everything else should
always be merged into one database. See these multiple keyrings as
a kind of keyservers - and they should be read-only.

Werner

--
ceterum censeo RSA esse delendam