security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-02 22:46:30 +02:00
Code Activity

indent: Fix spelling

Browse source 
--

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 2024-05-12 18:09:23 -04:00 • committed by Werner Koch
parent 253a701ed7
commit 42b0e9558a
No known key found for this signature in database
GPG key ID: E3FDFF218E45B72B
136 changed files with 233 additions and 233 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/ldap/README.ldap
View file

@ -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:

4
doc/ldap/gnupg-ldap-ad-schema.ldif
View file

@ -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.
#

4
doc/ldap/gnupg-ldap-schema.ldif
View file

@ -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'