diff options
author | Ineiev <[email protected]> | 2016-03-04 16:27:21 +0000 |
---|---|---|
committer | NIIBE Yutaka <[email protected]> | 2016-09-20 01:51:35 +0000 |
commit | f25e04005af5831053ba194a09e3afa48d1e162b (patch) | |
tree | ee8a1f54c0df7e763c8c4321fcbb8cf9daa488cc /doc/gpgsm.texi | |
parent | doc: Eliminate inconsistent UK English. (diff) | |
download | gnupg-f25e04005af5831053ba194a09e3afa48d1e162b.tar.gz gnupg-f25e04005af5831053ba194a09e3afa48d1e162b.zip |
doc: Fix mistakes.
* doc/dirmngr.texi, doc/gpg.texi, doc/gpgsm.texi,
doc/howto-create-a-server-cert.texi,
doc/scdaemon.texi, doc/tools.texi: Fix.
Diffstat (limited to 'doc/gpgsm.texi')
-rw-r--r-- | doc/gpgsm.texi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/gpgsm.texi b/doc/gpgsm.texi index 4e67d7557..24a559093 100644 --- a/doc/gpgsm.texi +++ b/doc/gpgsm.texi @@ -636,7 +636,7 @@ Sometimes signatures are broken in that they announce a different digest algorithm than actually used. @command{gpgsm} uses a one-pass data processing model and thus needs to rely on the announced digest algorithms to properly hash the data. As a workaround this option may -be used to tell gpg to also hash the data using the algorithm +be used to tell @command{gpgsm} to also hash the data using the algorithm @var{name}; this slows processing down a little bit but allows verification of such broken signatures. If @command{gpgsm} prints an error like ``digest algo 8 has not been enabled'' you may want to try this option, @@ -1262,7 +1262,7 @@ is no need to set recipients. @command{GPGSM} automatically strips any @acronym{S/MIME} headers from the input, so it is valid to pass an entire MIME part to the INPUT pipe. -The encryption is done by using the command +The decryption is done by using the command @example DECRYPT |