diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ChangeLog | 4 | ||||
| -rw-r--r-- | doc/DETAILS | 2 | ||||
| -rw-r--r-- | doc/gpg.sgml | 40 |
3 files changed, 41 insertions, 5 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index d9ef0eaf8..5e6dea587 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +2001-09-24 Werner Koch <[email protected]> + + * gpg.sgml: Described --{update,check}-trustdb. + 2001-09-03 Werner Koch <[email protected]> * gpg.sgml, gpgv.sgml: Removed GDBM stuff. diff --git a/doc/DETAILS b/doc/DETAILS index 8d2217844..66563663b 100644 --- a/doc/DETAILS +++ b/doc/DETAILS @@ -469,7 +469,7 @@ the DB is always of type 1 and this is the only record of this type. 1 u32 record number of shadow directory hash table It does not make sense to combine this table with the key table because the keyid is not in every case a part of the fingerprint. - 4 bytes reserved for version extension record + 1 u32 record number of the trusthashtbale Record type 2: (directory record) diff --git a/doc/gpg.sgml b/doc/gpg.sgml index f27249971..717f7e394 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -505,7 +505,7 @@ not be expected to successfully import such a key. <listitem><para> Import/merge keys. This adds the given keys to the keyring. -The fast version does not build +The fast version does not update the trustdb; this can be done at any time with the command --update-trustdb. </para> @@ -527,10 +527,34 @@ give the name of this keyserver. <varlistentry> -<term>--export-ownertrust</term> +<term>--recv-keys &ParmKeyIDs;</term> <listitem><para> -List the assigned ownertrust values in ASCII format -for backup purposes. +Import the keys with the given key IDs from a HKP +keyserver. Option --keyserver must be used to +give the name of this keyserver. +</para></listitem></varlistentry> + +<varlistentry> +<term>--update-trustdb</term> +<listitem><para> +Do trust DB maintenance. This command goes over all keys and builds +the Web-of-Trust. This is an intercative command because it may has to +ask for the "ownertrust" values of keys. The user has to give an +estimation in how far she trusts the owner of the displayed key to +correctly certify (sign) other keys. It does only ask for that value +if it has not yet been assigned to a key. Using the edit menu, that +value can be changed at any time later. +</para></listitem></varlistentry> + +<varlistentry> +<term>--check-trustdb</term> +<listitem><para> +Do trust DB maintenance without user interaction. Form time to time +the trust database must be updated so that expired keys and resulting +changes in the Web-of_trust can be tracked. GnuPG tries to figure +when this is required and then does it implicitly; this command can be +used to force such a check. The processing is identically to that of +--update-trustdb but it skips keys with a not yet defined "ownertrust". </para></listitem></varlistentry> @@ -1164,6 +1188,14 @@ However, due to the fact that the signature creation needs manual interaction, this performance penalty does not matter in most settings. </para></listitem></varlistentry> +<term>--no-auto-check-trustdb</term> +<listitem><para> +If GnuPG feels that its information about the Web-of-Trust has to be +updated, it automatically runs the --check-trustdb command +internally. As this is a time consuming process, this option allow to +disable the automatic invocation. +</para></listitem></varlistentry> + <varlistentry> <term>--throw-keyid</term> <listitem><para> |