From: Rich Bowen
Date: Mon, 5 Mar 2012 00:37:27 +0000 (+0000)
Subject: The referenced Makefile no longer exists, since mod_ssl is no longer a
X-Git-Tag: 2.5.0-alpha~7418
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=87d5ae28a7c7112ca10b8e3618525781af968e73;p=thirdparty%2Fapache%2Fhttpd.git
The referenced Makefile no longer exists, since mod_ssl is no longer a
separate distribution. If someone would like to provide more detail
here, that would be great. This is in response to
https://issues.apache.org/bugzilla/show_bug.cgi?id=49562
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1296911 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en
index 50b8ce33fce..1b63ab730f5 100644
--- a/docs/manual/mod/mod_ssl.html.en
+++ b/docs/manual/mod/mod_ssl.html.en
@@ -347,8 +347,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you can't just place the Certificate files
there: you also have to create symbolic links named
hash-value.N. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLCACertificatePath /usr/local/apache2/conf/ssl.crt/
@@ -413,9 +412,7 @@ details.
through hash filenames. So usually you can't just place the
Certificate files there: you also have to create symbolic links named
hash-value.N. And you should always make sure
-this directory contains the appropriate symbolic links. Use the
-Makefile which comes with mod_ssl to accomplish this
-task.
+this directory contains the appropriate symbolic links.
Example
SSLCADNRequestPath /usr/local/apache2/conf/ca-names.crt/
@@ -499,8 +496,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you have not only to place the CRL files there.
Additionally you have to create symbolic links named
hash-value.rN. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLCARevocationPath /usr/local/apache2/conf/ssl.crl/
@@ -1273,8 +1269,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you can't just place the Certificate files
there: you also have to create symbolic links named
hash-value.N. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLProxyCACertificatePath /usr/local/apache2/conf/ssl.crt/
@@ -1359,8 +1354,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you have not only to place the CRL files there.
Additionally you have to create symbolic links named
hash-value.rN. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLProxyCARevocationPath /usr/local/apache2/conf/ssl.crl/
@@ -1523,9 +1517,7 @@ keys used for authentication of the proxy server to remote servers.
The files in this directory must be PEM-encoded and are accessed through
hash filenames. Additionally, you must create symbolic links named
hash-value.N. And you should always make sure this
-directory contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
-
+directory contains the appropriate symbolic links.
Currently there is no support for encrypted private keys
diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index f54aa34c9d8..88f94f01dd5 100644
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -885,8 +885,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you can't just place the Certificate files
there: you also have to create symbolic links named
hash-value.N. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLCACertificatePath /usr/local/apache2/conf/ssl.crt/
@@ -980,9 +979,7 @@ details.
through hash filenames. So usually you can't just place the
Certificate files there: you also have to create symbolic links named
hash-value.N. And you should always make sure
-this directory contains the appropriate symbolic links. Use the
-Makefile which comes with mod_ssl to accomplish this
-task.
+this directory contains the appropriate symbolic links.
Example
SSLCADNRequestPath /usr/local/apache2/conf/ca-names.crt/
@@ -1007,8 +1004,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you have not only to place the CRL files there.
Additionally you have to create symbolic links named
hash-value.rN. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLCARevocationPath /usr/local/apache2/conf/ssl.crl/
@@ -1496,9 +1492,7 @@ keys used for authentication of the proxy server to remote servers.
The files in this directory must be PEM-encoded and are accessed through
hash filenames. Additionally, you must create symbolic links named
hash-value.N. And you should always make sure this
-directory contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
-
+directory contains the appropriate symbolic links.
Currently there is no support for encrypted private keys
@@ -1752,8 +1746,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you can't just place the Certificate files
there: you also have to create symbolic links named
hash-value.N. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLProxyCACertificatePath /usr/local/apache2/conf/ssl.crt/
@@ -1800,8 +1793,7 @@ The files in this directory have to be PEM-encoded and are accessed through
hash filenames. So usually you have not only to place the CRL files there.
Additionally you have to create symbolic links named
hash-value.rN. And you should always make sure this directory
-contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
+contains the appropriate symbolic links.
Example
SSLProxyCARevocationPath /usr/local/apache2/conf/ssl.crl/