mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
Spelling cleanup.
No functional changes, just fixing minor spelling issues. --- Most of these were identified from the command line by running: codespell \ --ignore-words-list fpr,stati,keyserver,keyservers,asign,cas,iff,ifset \ --skip '*.po,ChangeLog*,help.*.txt,*.jpg,*.eps,*.pdf,*.png,*.gpg,*.asc' \ doc g13 g10 kbx agent artwork scd tests tools am common dirmngr sm \ NEWS README README.maint TODO Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
This commit is contained in:
parent
0e1cbabc0a
commit
0904b8ef34
83 changed files with 122 additions and 122 deletions
|
@ -130,7 +130,7 @@ the colon format if you want to manually debug things.
|
|||
> * How to import a CRL
|
||||
|
||||
CRLs are managed by the dirmngr which is a separate package. The idea
|
||||
is to eventaully turn it into a system daemon, so that on a multi-user
|
||||
is to eventually turn it into a system daemon, so that on a multi-user
|
||||
machine CRLs are handled more efficiently. As of now the dirmngr
|
||||
needs service from gpgsm thus it is best to call it through gpgsm:
|
||||
|
||||
|
|
|
@ -1085,7 +1085,7 @@ as a binary blob.
|
|||
@c
|
||||
@c If no certificate was found, the function returns with the error
|
||||
@c GPG_ERR_MISSING_CERT. Now the signature is verified. If this fails,
|
||||
@c the erro is returned. On success the @code{validate_cert_chain} is
|
||||
@c the error is returned. On success the @code{validate_cert_chain} is
|
||||
@c used to verify that the certificate is actually valid.
|
||||
@c
|
||||
@c Here we may encounter a recursive situation:
|
||||
|
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
# Reject the usual metavariables. Usual not required because
|
||||
# gpg-agent can be used to reject all passphrases shorter than 8
|
||||
# charactes.
|
||||
# characters.
|
||||
foo
|
||||
bar
|
||||
baz
|
||||
|
|
|
@ -56,7 +56,7 @@ same commands as available in the interactive mode are run from the
|
|||
command line. These commands need to be delimited with a double-dash.
|
||||
If a double-dash or a shell specific character is required as part of
|
||||
a command the entire command needs to be put in quotes. If one of
|
||||
those commands returns an error the remaining commands are mot anymore
|
||||
those commands returns an error the remaining commands are not anymore
|
||||
run unless the command was prefixed with a single dash.
|
||||
|
||||
A list of commands is available by using the command @code{help} and a
|
||||
|
|
|
@ -3554,7 +3554,7 @@ on the configuration file.
|
|||
@c @opindex use-only-openpgp-card
|
||||
@c Only access OpenPGP card's and no other cards. This is a hidden
|
||||
@c option which could be used in case an old use case required the
|
||||
@c OpenPGP card while several cards are avaiable. This option might be
|
||||
@c OpenPGP card while several cards are available. This option might be
|
||||
@c removed if it turns out that nobody requires it.
|
||||
|
||||
@end table
|
||||
|
@ -3945,7 +3945,7 @@ The program returns 0 if there are no severe errors, 1 if at least a
|
|||
signature was bad, and other error codes for fatal errors.
|
||||
|
||||
Note that signature verification requires exact knowledge of what has
|
||||
been signed and by whom it has beensigned. Using only the return code
|
||||
been signed and by whom it has been signed. Using only the return code
|
||||
is thus not an appropriate way to verify a signature by a script.
|
||||
Either make proper use or the status codes or use the @command{gpgv}
|
||||
tool which has been designed to make signature verification easy for
|
||||
|
|
|
@ -83,7 +83,7 @@ or if no such user directory hierarchy exists @file{~/.gnupg/S.log}).
|
|||
|
||||
@item --force
|
||||
@opindex force
|
||||
Delete an already existing socket file. This option is implictly used
|
||||
Delete an already existing socket file. This option is implicitly used
|
||||
if no socket name has been given on the command line.
|
||||
|
||||
@item --homedir @var{DIR}
|
||||
|
|
|
@ -757,7 +757,7 @@ https://gnupg.org/faq/whats-new-in-2.1.html
|
|||
──────────────────────────
|
||||
|
||||
Since version 2.1.14 the export and import options have been enhanced
|
||||
to allow the use of /gpg/ to modify a key without first stroing it in
|
||||
to allow the use of /gpg/ to modify a key without first storing it in
|
||||
the keyring. For example:
|
||||
|
||||
┌────
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue