mirror of
git://git.gnupg.org/gnupg.git
synced 2024-12-22 10:19:57 +01:00
gpgv: Improve documentation for keyring choices
* doc/gpgv.texi: Improve documentation for keyring choices -- From the existing documentation, it's not clear whether the default keyring will always be mixed into the set of keyrings, or whether it will be skipped if a --keyring is present. The updated text here attempts to describe the keyring selection logic more completely. Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
This commit is contained in:
parent
b3a7a51407
commit
096c2aa705
@ -59,13 +59,14 @@ no configuration files and only a few options are implemented.
|
|||||||
That does also mean that it does not check for expired or revoked
|
That does also mean that it does not check for expired or revoked
|
||||||
keys.
|
keys.
|
||||||
|
|
||||||
By default a keyring named @file{trustedkeys.kbx} is used; if that
|
If no @code{--keyring} option is given, @code{gpgv} looks for a
|
||||||
does not exist a keyring named @file{trustedkeys.gpg} is used. The
|
``default'' keyring named @file{trustedkeys.kbx} (preferred) or
|
||||||
default keyring is assumed to be in the home directory of GnuPG,
|
@file{trustedkeys.gpg} in the home directory of GnuPG, either the
|
||||||
either the default home directory or the one set by an option or an
|
default home directory or the one set by the @code{--homedir} option
|
||||||
environment variable. The option @code{--keyring} may be used to
|
or the @code{GNUPGHOME} environment variable. If any @code{--keyring}
|
||||||
specify a different keyring or even multiple keyrings.
|
option is used, @code{gpgv} will not look for the default keyring. The
|
||||||
|
@code{--keyring} option may be used multiple times and all specified
|
||||||
|
keyrings will be used together.
|
||||||
|
|
||||||
@noindent
|
@noindent
|
||||||
@mansect options
|
@mansect options
|
||||||
|
Loading…
x
Reference in New Issue
Block a user