mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
indent: Fix spelling
-- These are non-substantive corrections for minor spelling mistakes within the GnuPG codebase. With something like this applied to the codebase, and a judiciously tuned spellchecker integrated as part of a standard test suite, it should be possible to keep a uniform orthography within the project. GnuPG-bug-id: 7116
This commit is contained in:
Daniel Kahn Gillmor
Werner Koch
parent
253a701ed7
commit
42b0e9558a
136 changed files with 233 additions and 233 deletions
14
doc/DETAILS
14
doc/DETAILS
|
|
@ -132,7 +132,7 @@ described here.
|
|||
*** Field 5 - KeyID
|
||||
|
||||
This is the 64 bit keyid as specified by OpenPGP and the last 64
|
||||
bit of the SHA-1 fingerprint of an X.509 certifciate.
|
||||
bit of the SHA-1 fingerprint of an X.509 certificate.
|
||||
|
||||
*** Field 6 - Creation date
|
||||
|
||||
|
|
@ -1101,7 +1101,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
|
|||
gpg-agent.
|
||||
- keyedit.passwd :: Changing the password failed.
|
||||
- nomdc_with_legacy_cipher :: The message was not MDC protected.
|
||||
Use the command line to lern about a workaround.
|
||||
Use the command line to learn about a workaround.
|
||||
- random-compliance :: The random number generator or the used
|
||||
version of Libgcrypt do not fulfill the requirements of the
|
||||
current compliance setting. The error code is often
|
||||
|
|
@ -1179,7 +1179,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
|
|||
<total>. For example "B", "KiB", or "MiB".
|
||||
|
||||
*** BACKUP_KEY_CREATED <fingerprint> <fname>
|
||||
A backup of a key identified by <fingerprint> has been writte to
|
||||
A backup of a key identified by <fingerprint> has been written to
|
||||
the file <fname>; <fname> is percent-escaped.
|
||||
|
||||
*** MOUNTPOINT <name>
|
||||
|
|
@ -1263,7 +1263,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
|
|||
|
||||
*** CERTINFO <certtype> <certref> [<label>]
|
||||
|
||||
This status is emitted for X.509 certifcates.
|
||||
This status is emitted for X.509 certificates.
|
||||
CERTTYPE is a number indicating the type of the certificate:
|
||||
0 := Unknown
|
||||
100 := Regular X.509 cert
|
||||
|
|
@ -1274,7 +1274,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
|
|||
|
||||
CERTREF identifies the certificate uniquely on the card and may be
|
||||
used to match it with a key's KEYREF. LABEL is an optional human
|
||||
readable decription of the certificate; it won't have any space in
|
||||
readable description of the certificate; it won't have any space in
|
||||
it and is percent encoded.
|
||||
|
||||
*** MANUFACTURER <n> [<string>]
|
||||
|
|
@ -1297,7 +1297,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
|
|||
*** KEY-ATTR-INFO <keyref> <string>
|
||||
This is the response from scdaemon on GETATTR KEY-ATTR-INFO for
|
||||
OpenPGP cards. <keyref> is the usual keyref (e.g. OPENPGP.1 or
|
||||
OPENPGP.129) and <string> is the algoritm or curve name, which
|
||||
OPENPGP.129) and <string> is the algorithm or curve name, which
|
||||
is available for the key.
|
||||
|
||||
*** KEY-TIME <n> <timestamp>
|
||||
|
|
@ -1310,7 +1310,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
|
|||
*** KEY-LABEL <keyref> <label>
|
||||
This returns the human readbable label for the keys given by
|
||||
KEYREF. LABEL won't have any space in it and is percent encoded.
|
||||
This info shall only be used for dispaly purposes.
|
||||
This info shall only be used for display purposes.
|
||||
|
||||
* Format of the --attribute-fd output
|
||||
|
||||
|
|
|
|||
|
|
@ -152,7 +152,7 @@ Note that such a comment will be removed if the git commit option
|
|||
if ( 42 == foo )
|
||||
#+end_src
|
||||
this is harder to read and modern compilers are pretty good in
|
||||
detecing accidental assignments. It is also suggested not to
|
||||
detecting accidental assignments. It is also suggested not to
|
||||
compare to 0 or NULL but to test the value direct or with a '!';
|
||||
this makes it easier to see that a boolean test is done.
|
||||
- We use our own printf style functions like =es_printf=, and
|
||||
|
|
@ -244,7 +244,7 @@ subject line; the list is used for several different projects.
|
|||
|
||||
In general you should send patches only for the master branch; we may
|
||||
later decide to backport to another branch. Please ask first before
|
||||
sending pacthes for another branch.
|
||||
sending patches for another branch.
|
||||
|
||||
If you're working from the Git repo, here's a suggested workflow:
|
||||
|
||||
|
|
|
|||
|
|
@ -1278,7 +1278,7 @@ as a binary blob.
|
|||
@c
|
||||
@c For historical reasons the Assuan command ISVALID is a bit different
|
||||
@c to CHECKCRL but this is mainly due to different calling conventions.
|
||||
@c In the end the same fucntionality is used, albeit hidden by a couple
|
||||
@c In the end the same functionality is used, albeit hidden by a couple
|
||||
@c of indirection and argument and result code mangling. It furthere
|
||||
@c ingetrages OCSP checking depending on options are the way it is
|
||||
@c called. GPGSM still uses this command but might eventually switch over
|
||||
|
|
|
|||
|
|
@ -10,8 +10,8 @@
|
|||
# and gpgsm.
|
||||
#use-keyboxd
|
||||
|
||||
# For testing ist is somethimes useful to use a different binary
|
||||
# of keybox. This option can be used to speicify this.
|
||||
# For testing it is sometimes useful to use a different binary
|
||||
# of keybox. This option can be used to specify this.
|
||||
#keyboxd-program /foo/bar/keyboxd
|
||||
|
||||
# For the daemons (gpg-agent, scdaemon, dirmngr, keyboxd) it is often
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
# one, as well as empty lines are ignored. Lines have a length limit
|
||||
# but this is not serious limitation as the format of the entries is
|
||||
# fixed and checked by gpg-agent. A non-comment line starts with
|
||||
# optional white space, followed by the SHA-1 fingerpint in hex,
|
||||
# optional white space, followed by the SHA-1 fingerprint in hex,
|
||||
# optionally followed by a flag character which my either be 'P', 'S'
|
||||
# or '*'. This file will be read by gpg-agent if no local trustlist
|
||||
# is available or if the statement "include-default" is used in the
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@
|
|||
|
||||
@c Create a separate index for command line options.
|
||||
@defcodeindex op
|
||||
@c Create an index vor environment variables and files.
|
||||
@c Create an index for environment variables and files.
|
||||
@defcodeindex ef
|
||||
|
||||
@c Merge the function index into the concept index.
|
||||
|
|
|
|||
|
|
@ -281,7 +281,7 @@ removes this data object. GnuPG does not use this info.
|
|||
Change the User Interaction Flag. That flags tells whether the
|
||||
confirmation button of a token shall be used. @var{n} must in the
|
||||
range 1 to 3. "permanent" is the same as "on" but the flag can't be
|
||||
changed anmore.
|
||||
changed anymore.
|
||||
|
||||
@item UNBLOCK
|
||||
@opindex unblock
|
||||
|
|
|
|||
|
|
@ -1611,7 +1611,7 @@ maintained by the keyboxd process in its own database.
|
|||
|
||||
@item --primary-keyring @var{file}
|
||||
@opindex primary-keyring
|
||||
This is a varian of @option{--keyring} and designates @var{file} as
|
||||
This is a variant of @option{--keyring} and designates @var{file} as
|
||||
the primary public keyring. This means that newly imported keys (via
|
||||
@option{--import} or keyserver @option{--recv-from}) will go to this
|
||||
keyring.
|
||||
|
|
@ -1808,7 +1808,7 @@ this option at all (e.g. due to the @option{--no-options} option).
|
|||
@opindex add-desig-revoker
|
||||
Add the key specified by @var{fingerprint} as a designated revoker to
|
||||
newly created keys. If the fingerprint is prefixed with the keyword
|
||||
``sensitive:'' that info is normally not exported wit the key. This
|
||||
``sensitive:'' that info is normally not exported with the key. This
|
||||
option may be given several time to add more than one designated
|
||||
revoker. If the keyword ``clear'' is used instead of a fingerprint,
|
||||
all designated options previously encountered are discarded.
|
||||
|
|
@ -2794,7 +2794,7 @@ The available properties are:
|
|||
Key Directory.
|
||||
|
||||
@item url
|
||||
A string with the the URL associated wit the last key lookup.
|
||||
A string with the the URL associated with the last key lookup.
|
||||
|
||||
@end table
|
||||
|
||||
|
|
|
|||
|
|
@ -117,7 +117,7 @@ disable CRL checking in gpgsm's configuration.
|
|||
|
||||
|
||||
.gpg.edit_ownertrust.value
|
||||
# The help identies prefixed with "gpg." used to be hard coded in gpg
|
||||
# The help entries prefixed with "gpg." used to be hard coded in gpg
|
||||
# but may now be overridden by help texts from this file.
|
||||
It's up to you to assign a value here; this value will never be exported
|
||||
to any 3rd party. We need it to implement the web-of-trust; it has nothing
|
||||
|
|
|
|||
|
|
@ -291,7 +291,7 @@ olcAccess: {0} to dn.subtree="dc=example,dc=com"
|
|||
|
||||
As usual replace all "dc=example,dc=com" accordingly. Take care not
|
||||
to insert a blank line anywhere. The first line needs to give the DN
|
||||
of the database as determined above. Excute the rules from that file
|
||||
of the database as determined above. Execute the rules from that file
|
||||
using the command:
|
||||
|
||||
: ldapmodify -Q -Y EXTERNAL -H ldapi:/// -f grantaccess.ldif
|
||||
|
|
@ -384,7 +384,7 @@ This lists just the DNs. If you need the entire content of the DIT
|
|||
leave out the "dn" argument. The option "-LLL" selects useful
|
||||
formatting options for the output.
|
||||
|
||||
** Insert X.509 Certficate
|
||||
** Insert X.509 Certificate
|
||||
|
||||
If you don't have a handy tool to insert a certificate via LDAP you
|
||||
can do it manually. First put the certificate in binary (DER) format
|
||||
|
|
@ -505,7 +505,7 @@ to revert replace "ACL" by "none".
|
|||
** Extending the AD Schema
|
||||
The Active Directory on Windows is actually an LDAP server but
|
||||
configuration differs from OpenLDAP. The used schema is the same but
|
||||
the data objects are slighly different. To extend the schema the
|
||||
the data objects are slightly different. To extend the schema the
|
||||
LDIF format is used but with variants of the files used for OpenLDAP.
|
||||
Thus please download these two files:
|
||||
|
||||
|
|
@ -517,7 +517,7 @@ schema. There are *no ways to revert changes* made to a schema. You
|
|||
should also first try this all on a test system and not on a
|
||||
production system.
|
||||
|
||||
To extend the schema become Adminstrator on your Primary Domain
|
||||
To extend the schema become Administrator on your Primary Domain
|
||||
Controller and open a shell (Command Prompt). Copy the above
|
||||
mentioned ldif files to your working directory and run the following
|
||||
command:
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# gnupg-ldap-ad-scheme.ldif -*- conf -*-
|
||||
#
|
||||
# Schema for an OpenPGP LDAP keyserver. This is a slighly enhanced
|
||||
# Schema for an OpenPGP LDAP keyserver. This is a slightly enhanced
|
||||
# version of the original LDAP schema used for PGP keyservers as
|
||||
# installed at quite some sites.
|
||||
# Revision: 2021-09-01 v1
|
||||
|
|
@ -12,7 +12,7 @@
|
|||
# ldifde -i -v -f gnupg-ldap-ad-schema.ldif
|
||||
# -c "DC=EXAMPLEDC" "#configurationNamingContext"
|
||||
# (the above command is given as one line)
|
||||
# - The schema does not get its own distingished name as done with OpenLDAP.
|
||||
# - The schema does not get its own distinguished name as done with OpenLDAP.
|
||||
# - The first GUID we use is f406e7a5-a5ea-411e-9ddd-2e4e66899800
|
||||
# and incremented for each attribute.
|
||||
#
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# gnupg-ldap-scheme.ldif -*- conf -*-
|
||||
#
|
||||
# Schema for an OpenPGP LDAP keyserver. This is a slighly enhanced
|
||||
# Schema for an OpenPGP LDAP keyserver. This is a slightly enhanced
|
||||
# version of the original LDAP schema used for PGP keyservers as
|
||||
# installed at quite some sites.
|
||||
# Revision: 2020-10-07
|
||||
|
|
@ -58,7 +58,7 @@ olcAttributeTypes: {5}(
|
|||
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
|
||||
SINGLE-VALUE )
|
||||
# The short key id. This is actually not required and should thus not
|
||||
# be used by cleint software.
|
||||
# be used by client software.
|
||||
olcAttributeTypes: {6}(
|
||||
1.3.6.1.4.1.3401.8.2.14
|
||||
NAME 'pgpKeyID'
|
||||
|
|
|
|||
|
|
@ -1826,7 +1826,7 @@ Do the check using the OCSP protocol and ignore any CRLs.
|
|||
@item --force-default-responder
|
||||
@opindex force-default-responder
|
||||
When checking using the OCSP protocol, force the use of the default OCSP
|
||||
responder. That is not to use the Reponder as given by the certificate.
|
||||
responder. That is not to use the Responder as given by the certificate.
|
||||
|
||||
@item --ping
|
||||
@opindex ping
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue