mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
doc: Fix spelling errors found by lintian.
-- Reported-by: Andreas Metzler <ametzler@debian.org>
This commit is contained in:
parent
97b2837653
commit
2ed1f68b48
20 changed files with 36 additions and 36 deletions
|
@ -172,7 +172,7 @@ socket.
|
|||
Set compatibility flags to work around certain problems or to emulate
|
||||
bugs. The @var{flags} are given as a comma separated list of flag
|
||||
names and are OR-ed together. The special flag "none" clears the list
|
||||
and allows to start over with an empty list. To get a list of
|
||||
and allows one to start over with an empty list. To get a list of
|
||||
available flags the sole word "help" can be used.
|
||||
|
||||
@item --faked-system-time @var{epoch}
|
||||
|
|
|
@ -302,7 +302,7 @@ debugging.
|
|||
@item --steal-socket
|
||||
@opindex steal-socket
|
||||
In @option{--daemon} mode, gpg-agent detects an already running
|
||||
gpg-agent and does not allow to start a new instance. This option can
|
||||
gpg-agent and does not allow one to start a new instance. This option can
|
||||
be used to override this check: the new gpg-agent process will try to
|
||||
take over the communication sockets from the already running process
|
||||
and start anyway. This option should in general not be used.
|
||||
|
@ -643,7 +643,7 @@ gpg-agent as a replacement for PuTTY's Pageant, the option
|
|||
In this mode of operation, the agent does not only implement the
|
||||
gpg-agent protocol, but also the agent protocol used by OpenSSH
|
||||
(through a separate socket or via Named Pipes) or the protocol used by
|
||||
PuTTY. Consequently, this allows to use the gpg-agent as a drop-in
|
||||
PuTTY. Consequently, this allows one to use the gpg-agent as a drop-in
|
||||
replacement for the ssh-agent.
|
||||
|
||||
SSH keys, which are to be used through the agent, need to be added to
|
||||
|
@ -693,7 +693,7 @@ The order in which keys are presented to ssh are:
|
|||
@item Negative Use-for-ssh values
|
||||
If a key file has the attribute "Use-for-ssh" and its value is
|
||||
negative, these keys are presented first to ssh. The negative
|
||||
values are capped at -999 with -999 beeing lower ranked than -1.
|
||||
values are capped at -999 with -999 being lower ranked than -1.
|
||||
These values can be used to prefer on-disk keys over keys taken
|
||||
from active cards.
|
||||
|
||||
|
|
|
@ -226,7 +226,7 @@ OpenPGP or X.509 keys.
|
|||
@item LOGIN [--clear] [< @var{file}]
|
||||
@opindex login
|
||||
Set the login data object of OpenPGP cards. If @var{file} is given
|
||||
the data is is read from that file. This allows to store binary data
|
||||
the data is is read from that file. This allows one to store binary data
|
||||
in the login field. The option @option{--clear} deletes the login
|
||||
data object.
|
||||
|
||||
|
|
16
doc/gpg.texi
16
doc/gpg.texi
|
@ -716,7 +716,7 @@ inserted smartcard, the special string ``card'' can be used for
|
|||
will figure them out and creates an OpenPGP key consisting of the
|
||||
usual primary key and one subkey. This works only with certain
|
||||
smartcards. Note that the interactive @option{--full-gen-key} command
|
||||
allows to do the same but with greater flexibility in the selection of
|
||||
allows one to do the same but with greater flexibility in the selection of
|
||||
the smartcard keys.
|
||||
|
||||
Note that it is possible to create a primary key and a subkey using
|
||||
|
@ -1947,20 +1947,20 @@ list. The default is "local,wkd".
|
|||
|
||||
@item ntds
|
||||
Locate the key using the Active Directory (Windows only). This
|
||||
method also allows to search by fingerprint using the command
|
||||
method also allows one to search by fingerprint using the command
|
||||
@option{--locate-external-key}. Note that this mechanism is
|
||||
actually a shortcut for the mechanism @samp{keyserver} but using
|
||||
"ldap:///" as the keyserver.
|
||||
|
||||
@item keyserver
|
||||
Locate a key using a keyserver. This method also allows to search
|
||||
Locate a key using a keyserver. This method also allows one to search
|
||||
by fingerprint using the command @option{--locate-external-key} if
|
||||
any of the configured keyservers is an LDAP server.
|
||||
|
||||
@item keyserver-URL
|
||||
In addition, a keyserver URL as used in the @command{dirmngr}
|
||||
configuration may be used here to query that particular keyserver.
|
||||
This method also allows to search by fingerprint using the command
|
||||
This method also allows one to search by fingerprint using the command
|
||||
@option{--locate-external-key} if the URL specifies an LDAP server.
|
||||
|
||||
@item local
|
||||
|
@ -3151,7 +3151,7 @@ Prompt before overwriting any files.
|
|||
Set compatibility flags to work around problems due to non-compliant
|
||||
keys or data. The @var{flags} are given as a comma separated
|
||||
list of flag names and are OR-ed together. The special flag "none"
|
||||
clears the list and allows to start over with an empty list. To get a
|
||||
clears the list and allows one to start over with an empty list. To get a
|
||||
list of available flags the sole word "help" can be used.
|
||||
|
||||
@item --debug-level @var{level}
|
||||
|
@ -3207,7 +3207,7 @@ and may thus be changed or removed at any time without notice.
|
|||
|
||||
@item --debug-allow-large-chunks
|
||||
@opindex debug-allow-large-chunks
|
||||
To facilitate software tests and experiments this option allows to
|
||||
To facilitate software tests and experiments this option allows one to
|
||||
specify a limit of up to 4 EiB (@code{--chunk-size 62}).
|
||||
|
||||
@item --debug-ignore-expiration
|
||||
|
@ -3646,7 +3646,7 @@ not need to be listed explicitly.
|
|||
@opindex allow-weak-key-signatures
|
||||
To avoid a minor risk of collision attacks on third-party key
|
||||
signatures made using SHA-1, those key signatures are considered
|
||||
invalid. This options allows to override this restriction.
|
||||
invalid. This options allows one to override this restriction.
|
||||
|
||||
@item --override-compliance-check
|
||||
This was a temporary introduced option and has no more effect.
|
||||
|
@ -4111,7 +4111,7 @@ Operation is further controlled by a few environment variables:
|
|||
|
||||
@item GNUPG_EXEC_DEBUG_FLAGS
|
||||
@efindex GNUPG_EXEC_DEBUG_FLAGS
|
||||
This variable allows to enable diagnostics for process management.
|
||||
This variable allows one to enable diagnostics for process management.
|
||||
A numeric decimal value is expected. Bit 0 enables general
|
||||
diagnostics, bit 1 enables certain warnings on Windows.
|
||||
|
||||
|
|
|
@ -767,7 +767,7 @@ is given as fingerprint or keygrip.
|
|||
Set compatibility flags to work around problems due to non-compliant
|
||||
certificates or data. The @var{flags} are given as a comma separated
|
||||
list of flag names and are OR-ed together. The special flag "none"
|
||||
clears the list and allows to start over with an empty list. To get a
|
||||
clears the list and allows one to start over with an empty list. To get a
|
||||
list of available flags the sole word "help" can be used.
|
||||
|
||||
@item --debug-level @var{level}
|
||||
|
|
|
@ -309,7 +309,7 @@ with lower priority should be used by default.
|
|||
|
||||
@item --application-priority @var{namelist}
|
||||
@opindex application-priority
|
||||
This option allows to change the order in which applications of a card
|
||||
This option allows one to change the order in which applications of a card
|
||||
a tried if no specific application was requested. @var{namelist} is a
|
||||
space or comma delimited list of application names. Unknown names are
|
||||
simply skipped. Applications not mentioned in the list are put in the
|
||||
|
|
|
@ -400,7 +400,7 @@ expected in the current GnuPG home directory. This command is usually
|
|||
not required because GnuPG is able to detect and remove stale lock
|
||||
files. Before using the command make sure that the file protected by
|
||||
the lock file is actually not in use. The lock command may be used to
|
||||
lock an accidently removed lock file. Note that the commands have no
|
||||
lock an accidentally removed lock file. Note that the commands have no
|
||||
effect on Windows because the mere existence of a lock file does not
|
||||
mean that the lock is active.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue