diff options
| author | Dr. Stephen Henson <steve@openssl.org> | 2002-11-09 18:05:33 +0000 |
|---|---|---|
| committer | Dr. Stephen Henson <steve@openssl.org> | 2002-11-09 18:05:33 +0000 |
| commit | a8c125550ca0714b5f7eeb8f7e6e6a06b356fb64 (patch) | |
| tree | 3f8e2431cb0b1f1c1878e24735b828b200159b1f /doc | |
| parent | 3782350c14c4a3fb77c7d3679d54ab21baa99330 (diff) | |
Typo
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/apps/req.pod | 8 | ||||
| -rw-r--r-- | doc/apps/smime.pod | 4 | ||||
| -rw-r--r-- | doc/apps/x509.pod | 12 |
3 files changed, 12 insertions, 12 deletions
diff --git a/doc/apps/req.pod b/doc/apps/req.pod index 10e4e12a5c..7a3b6bb99d 100644 --- a/doc/apps/req.pod +++ b/doc/apps/req.pod @@ -512,13 +512,13 @@ Sample configuration containing all field values: The header and footer lines in the B<PEM> format are normally: - -----BEGIN CERTIFICATE REQUEST---- - -----END CERTIFICATE REQUEST---- + -----BEGIN CERTIFICATE REQUEST----- + -----END CERTIFICATE REQUEST----- some software (some versions of Netscape certificate server) instead needs: - -----BEGIN NEW CERTIFICATE REQUEST---- - -----END NEW CERTIFICATE REQUEST---- + -----BEGIN NEW CERTIFICATE REQUEST----- + -----END NEW CERTIFICATE REQUEST----- which is produced with the B<-newhdr> option but is otherwise compatible. Either form is accepted transparently on input. diff --git a/doc/apps/smime.pod b/doc/apps/smime.pod index fa5d23e8dc..2453dd2738 100644 --- a/doc/apps/smime.pod +++ b/doc/apps/smime.pod @@ -340,8 +340,8 @@ detached signature format. You can use this program to verify the signature by line wrapping the base64 encoded structure and surrounding it with: - -----BEGIN PKCS7---- - -----END PKCS7---- + -----BEGIN PKCS7----- + -----END PKCS7----- and using the command, diff --git a/doc/apps/x509.pod b/doc/apps/x509.pod index 9f7eba4c87..0b53fb1cf8 100644 --- a/doc/apps/x509.pod +++ b/doc/apps/x509.pod @@ -643,18 +643,18 @@ Set a certificate to be trusted for SSL client use and change set its alias to The PEM format uses the header and footer lines: - -----BEGIN CERTIFICATE---- - -----END CERTIFICATE---- + -----BEGIN CERTIFICATE----- + -----END CERTIFICATE----- it will also handle files containing: - -----BEGIN X509 CERTIFICATE---- - -----END X509 CERTIFICATE---- + -----BEGIN X509 CERTIFICATE----- + -----END X509 CERTIFICATE----- Trusted certificates have the lines - -----BEGIN TRUSTED CERTIFICATE---- - -----END TRUSTED CERTIFICATE---- + -----BEGIN TRUSTED CERTIFICATE----- + -----END TRUSTED CERTIFICATE----- The conversion to UTF8 format used with the name options assumes that T61Strings use the ISO8859-1 character set. This is wrong but Netscape |