Skip to content

Commit e2daf21

Browse files
committed
gpg(docs): use correct --verify syntax
The gpg --verify usage example within the 'gpg.program' variable reference provides an incorrect example of the gpg --verify command arguments. The command argument order, when providing both a detached signature and data, should be signature first and data second: https://gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html Signed-off-by: Robert Morgan <[email protected]>
1 parent 6d5b264 commit e2daf21

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Documentation/config/gpg.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ gpg.program::
22
Use this custom program instead of "`gpg`" found on `$PATH` when
33
making or verifying a PGP signature. The program must support the
44
same command-line interface as GPG, namely, to verify a detached
5-
signature, "`gpg --verify $file - <$signature`" is run, and the
5+
signature, "`gpg --verify $signature - <$file`" is run, and the
66
program is expected to signal a good signature by exiting with
77
code 0, and to generate an ASCII-armored detached signature, the
88
standard input of "`gpg -bsau $key`" is fed with the contents to be

0 commit comments

Comments
 (0)