semantics of gnupg --keyserver in 2.1

[Daniel Kahn Gillmor]

On 12/17/2014 11:08 AM, Andre Heinecke wrote:
> In that case I would vote for just overwriting the config value if it is 
> provided on the command line and use a fallback mechanism using one or 
> multiple config entries otherwise. (or multiple keyserver options on the 
> command line)
> 
> 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?

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.

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20141217/6846e041/attachment.sig>