diff options
author | Daniel Kahn Gillmor <[email protected]> | 2024-05-12 22:09:23 +0000 |
---|---|---|
committer | Werner Koch <[email protected]> | 2024-05-31 10:28:32 +0000 |
commit | 42b0e9558a308dbc954ee60c3d346b5cabcd2fdb (patch) | |
tree | f073776758cd706a0cadf0bd64073d1669a8d691 /doc/ldap/README.ldap | |
parent | g13: Adjust for changed gnupg_process_spawn. (diff) | |
download | gnupg-42b0e9558a308dbc954ee60c3d346b5cabcd2fdb.tar.gz gnupg-42b0e9558a308dbc954ee60c3d346b5cabcd2fdb.zip |
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
Diffstat (limited to 'doc/ldap/README.ldap')
-rw-r--r-- | doc/ldap/README.ldap | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/ldap/README.ldap b/doc/ldap/README.ldap index 7095d6d10..33ffe3702 100644 --- a/doc/ldap/README.ldap +++ b/doc/ldap/README.ldap @@ -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: |