summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2020-02-26 18:53:22 +0100
committerWerner Koch <wk@gnupg.org>2020-03-18 13:50:52 +0100
commit810ea2cc684480c6aadceb2a10dd00f3fa67f2fb (patch)
treef981383126c8d06b107f0bf548afe8e35d70d3bf /doc
parentgpg: Fix key expiration and usage for keys created at the Epoch. (diff)
downloadgnupg2-810ea2cc684480c6aadceb2a10dd00f3fa67f2fb.tar.xz
gnupg2-810ea2cc684480c6aadceb2a10dd00f3fa67f2fb.zip
gpg: Update --trusted-key to accept fingerprint as well as long key id.
* g10/trustdb.c (tdb_register_trusted_key): accept fingerprint as well as long key ID. * doc/gpg.texi: document that --trusted-key can accept a fingerprint. -- GnuPG-bug-id: 4855 Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net> Fixed uses or return and kept the old string to avoid breaking translations. Signed-off-by: Werner Koch <wk@gnupg.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/gpg.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/gpg.texi b/doc/gpg.texi
index 2361af6d5..ab3912fc5 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -1651,10 +1651,10 @@ certification level below this as invalid. Defaults to 2, which
disregards level 1 signatures. Note that level 0 "no particular
claim" signatures are always accepted.
-@item --trusted-key @var{long key ID}
+@item --trusted-key @var{long key ID or fingerprint}
@opindex trusted-key
Assume that the specified key (which must be given
-as a full 8 byte key ID) is as trustworthy as one of
+as a full 8 byte key ID or 20 byte fingerprint) is as trustworthy as one of
your own secret keys. This option is useful if you
don't want to keep your secret keys (or one of them)
online but still want to be able to check the validity of a given