diff options
| author | Sol Jerome <sol.jerome@gmail.com> | 2014-11-03 09:15:51 -0600 |
|---|---|---|
| committer | Sol Jerome <sol.jerome@gmail.com> | 2014-11-03 09:15:51 -0600 |
| commit | 84ba7561d9450d05b0dd99b69c16437b29100704 (patch) | |
| tree | d4cca2cca3201b48226a471a6297c83c3e6ff8ad | |
| parent | a5c00f1c8f581d3d9b3c76e53404ad3489d15c52 (diff) | |
| download | bcfg2-84ba7561d9450d05b0dd99b69c16437b29100704.tar.gz bcfg2-84ba7561d9450d05b0dd99b69c16437b29100704.tar.bz2 bcfg2-84ba7561d9450d05b0dd99b69c16437b29100704.zip | |
doc: Fix typos
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
| -rw-r--r-- | doc/server/plugins/generators/sslca.txt | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/server/plugins/generators/sslca.txt b/doc/server/plugins/generators/sslca.txt index c27e6be4b..73527284c 100644 --- a/doc/server/plugins/generators/sslca.txt +++ b/doc/server/plugins/generators/sslca.txt @@ -35,7 +35,7 @@ For SSLCA to work, the openssl.cnf (or other configuration file) for that CA must contain full (not relative) paths. #. Add SSLCA to the **plugins** line in ``/etc/bcfg2.conf`` and - restart the server -- This enabled the SSLCA plugin on the Bcfg2 + restart the server -- This enables the SSLCA plugin on the Bcfg2 server. #. Add a section to your ``/etc/bcfg2.conf`` called ``sslca_foo``, @@ -48,12 +48,12 @@ that CA must contain full (not relative) paths. #. If necessary, add an entry for ``passphrase`` containing the passphrase for the CA's private key. We store this in ``/etc/bcfg2.conf`` as the permissions on that file should have it - only readable by the bcfg2 user. If no passphrase is entry exists, + only readable by the bcfg2 user. If no passphrase entry exists, it is assumed that the private key is stored unencrypted. #. Optionally, Add an entry ``chaincert`` that points to the location of your ssl chaining certificate. This is used when preexisting - certifcate hostfiles are found, so that they can be validated and + certificate hostfiles are found, so that they can be validated and only regenerated if they no longer meet the specification. If you're using a self signing CA this would be the CA cert that you generated. If the chain cert is a root CA cert (e.g., if it is a @@ -118,11 +118,11 @@ Configuration bcfg2.conf ---------- -``bcfg2.conf`` contains miscellaneous configuration options for the -SSLCA plugin. These are described in some detail above in -`getting-started`, but are also enumerated here as a reference. Any -booleans in the config file accept the values "1", "yes", "true", and -"on" for True, and "0", "no", "false", and "off" for False. +``bcfg2.conf`` contains miscellaneous configuration options for the SSLCA +plugin. These are described in some detail above in `getting-started`_, +but are also enumerated here as a reference. Any booleans in the config +file accept the values "1", "yes", "true", and "on" for True, and "0", +"no", "false", and "off" for False. Each directive below should appear at most once in each ``[sslca_<name>]`` section. The following directives are understood: |