Loading doc/apps/req.pod +4 −4 Original line number Diff line number Diff line Loading @@ -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. Loading doc/apps/smime.pod +2 −2 Original line number Diff line number Diff line Loading @@ -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, Loading doc/apps/x509.pod +6 −6 Original line number Diff line number Diff line Loading @@ -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 Loading Loading
doc/apps/req.pod +4 −4 Original line number Diff line number Diff line Loading @@ -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. Loading
doc/apps/smime.pod +2 −2 Original line number Diff line number Diff line Loading @@ -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, Loading
doc/apps/x509.pod +6 −6 Original line number Diff line number Diff line Loading @@ -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 Loading
