From: Werner Koch <wk@gnupg.org>
Date: Thu, 5 Jan 2017 19:25:16 +0000 (+0100)
Subject: doc: Mention gpgv in the description of gpg --verify.
X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ian/git?p=gnupg2.git;a=commitdiff_plain;h=2124e87c191dc6939b52ad06726e15ffff9a5936

doc: Mention gpgv in the description of gpg --verify.

--

Signed-off-by: Werner Koch <wk@gnupg.org>
(cherry picked from commit 353f6ff37646ad4c24d309a495e6c6f41e5235e3)

Gbp-Pq: Name 0023-doc-Mention-gpgv-in-the-description-of-gpg-verify.patch
---

diff --git a/doc/gpg.texi b/doc/gpg.texi
index 469e548..4ea2cd2 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -255,6 +255,13 @@ out the actual signed data, but there are other pitfalls with this
 format as well.  It is suggested to avoid cleartext signatures in
 favor of detached signatures.
 
+Note: Sometimes the use of the @command{gpgv} tool is easier than
+using the full-fledged @command{gpg} with this option.  @command{gpgv}
+is designed to compare signed data against a list of trusted keys and
+returns with success only for a good signature.  It has its own manual
+page.
+
+
 @item --multifile
 @opindex multifile
 This modifies certain other commands to accept multiple files for