generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Typo

Browse Source
This commit is contained in:
Dr. Stephen Henson 2002-11-09 18:05:33 +00:00
parent 3782350c14
commit a8c125550c
3 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/apps/req.pod
View File

@ -512,13 +512,13 @@ Sample configuration containing all field values:
The header and footer lines in the B<PEM> format are normally: The header and footer lines in the B<PEM> format are normally:
-----BEGIN CERTIFICATE REQUEST---- -----BEGIN CERTIFICATE REQUEST-----
-----END CERTIFICATE REQUEST---- -----END CERTIFICATE REQUEST-----
some software (some versions of Netscape certificate server) instead needs: some software (some versions of Netscape certificate server) instead needs:
-----BEGIN NEW CERTIFICATE REQUEST---- -----BEGIN NEW CERTIFICATE REQUEST-----
-----END NEW CERTIFICATE REQUEST---- -----END NEW CERTIFICATE REQUEST-----
which is produced with the B<-newhdr> option but is otherwise compatible. which is produced with the B<-newhdr> option but is otherwise compatible.
Either form is accepted transparently on input. Either form is accepted transparently on input.

4
doc/apps/smime.pod
View File

@ -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 signature by line wrapping the base64 encoded structure and surrounding
it with: it with:
-----BEGIN PKCS7---- -----BEGIN PKCS7-----
-----END PKCS7---- -----END PKCS7-----
and using the command, and using the command,

12
doc/apps/x509.pod
View File

@ -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: The PEM format uses the header and footer lines:
-----BEGIN CERTIFICATE---- -----BEGIN CERTIFICATE-----
-----END CERTIFICATE---- -----END CERTIFICATE-----
it will also handle files containing: it will also handle files containing:
-----BEGIN X509 CERTIFICATE---- -----BEGIN X509 CERTIFICATE-----
-----END X509 CERTIFICATE---- -----END X509 CERTIFICATE-----
Trusted certificates have the lines Trusted certificates have the lines
-----BEGIN TRUSTED CERTIFICATE---- -----BEGIN TRUSTED CERTIFICATE-----
-----END TRUSTED CERTIFICATE---- -----END TRUSTED CERTIFICATE-----
The conversion to UTF8 format used with the name options assumes that The conversion to UTF8 format used with the name options assumes that
T61Strings use the ISO8859-1 character set. This is wrong but Netscape T61Strings use the ISO8859-1 character set. This is wrong but Netscape