semantics of gnupg --keyserver in 2.1

Andre Heinecke aheinecke at
Wed Dec 17 19:48:32 CET 2014

On Wednesday, December 17, 2014 12:31:24 PM Daniel Kahn Gillmor wrote:
> On 12/17/2014 11:08 AM, Andre Heinecke wrote:
> > If you explicitly set the command line keyserver parameter you probably
> > really want that keyserver to be used for some reason. So this should
> > overwrite the config.
> Just to clarify, i think you mean "override", not "overwrite" -- there
> is no need to modify the configuration file because of the presence of
> the command-line argument, correct?

Yes you are correct. Apologies for the bad wording.

> I like the idea that if a --keyserver command line argument is present,
> it would supersede the configuration information that dirmngr started up
> with -- but only for these specific queries.  other queries routed
> through the same dirmngr process concurrently (or afterward) should
> retain their initial configuration.

I also agree with you there. Afaik this happens now as the gnupg process 
always sends a --clear with the first KEYSERVER command.


Andre Heinecke |  ++49-541-335083-262  |
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20141217/94572009/attachment.sig>

More information about the Gnupg-devel mailing list