From 2581786b9f9e86e4bbee0a21ed254c04da27ce48 Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Thu, 16 Apr 2015 18:29:46 +0000 Subject: [PATCH] Rebuild git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1674129 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/ssl/ssl_faq.html.en | 6 +++--- docs/manual/ssl/ssl_faq.xml.fr | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/manual/ssl/ssl_faq.html.en b/docs/manual/ssl/ssl_faq.html.en index c134f573dc..b592b84ff7 100644 --- a/docs/manual/ssl/ssl_faq.html.en +++ b/docs/manual/ssl/ssl_faq.html.en @@ -347,7 +347,7 @@ SSLCertificateKeyFile "/path/to/this/server.key"

The short answer is to use the CA.sh or CA.pl script provided by OpenSSL. Unless you have a good reason not to, you should use these for preference. If you cannot, you can create a - self-signed Certificate as follows:

+ self-signed certificate as follows:

  1. Create a RSA private key for your server @@ -368,11 +368,11 @@ SSLCertificateKeyFile "/path/to/this/server.key" $ openssl rsa -in server.key -out server.key.unsecure

    2. -
  2. Create a self-signed Certificate (X509 structure) +
  3. Create a self-signed certificate (X509 structure) with the RSA key you just created (output will be PEM formatted):

    $ openssl req -new -x509 -nodes -sha1 -days 365 - -key server.key -out server.crt
    + -key server.key -out server.crt -extensions usr_cert

    This signs the server CSR and results in a server.crt file.
    You can see the details of this Certificate using:
    diff --git a/docs/manual/ssl/ssl_faq.xml.fr b/docs/manual/ssl/ssl_faq.xml.fr index e0ebe37be3..26c6bd8f65 100644 --- a/docs/manual/ssl/ssl_faq.xml.fr +++ b/docs/manual/ssl/ssl_faq.xml.fr @@ -1,7 +1,7 @@ - + -- 2.50.1