From e1aee30233bb7854a82480e04eb72423d670e8c0 Mon Sep 17 00:00:00 2001
From: Joe Orton
Date: Wed, 3 Feb 2010 14:30:37 +0000
Subject: [PATCH] * mod_ssl.xml: Document the SSL_SECURE_RENEG envvar, and
SSLInsecureRenegotiation.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@906067 13f79535-47bb-0310-9956-ffa450edef68
---
docs/manual/mod/mod_ssl.xml | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index fe2862750e..6eee29ca05 100644
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -62,6 +62,7 @@ compatibility variables.
SSL_PROTOCOL | string | The SSL protocol version (SSLv2, SSLv3, TLSv1) |
SSL_SESSION_ID | string | The hex-encoded SSL session id |
SSL_SESSION_RESUMED | string | Initial or Resumed SSL Session. Note: multiple requests may be served over the same (Initial or Resumed) SSL session if HTTP KeepAlive is in use |
+SSL_SECURE_RENEG | string | true if secure renegotiation is supported, else false |
SSL_CIPHER | string | The cipher specification name |
SSL_CIPHER_EXPORT | string | true if cipher is an export cipher |
SSL_CIPHER_USEKEYSIZE | number | Number of cipher bits (actually used) |
@@ -1773,4 +1774,37 @@ certificate being validated references an OCSP responder.
+
+SSLInsecureRenegotiation
+Option to enable support for insecure renegotiation
+SSLInsecureRenegotiation flag
+server config
+virtual host
+Available in httpd 2.3 and later, if using OpenSSL 1.0.0 Beta 5 or later
+
+
+As originally specified, all versions of the SSL and TLS protocols
+(up to and including TLS/1.2) were vulnerable to a Man-in-the-Middle
+attack
+(CVE-2009-3555)
+during a renegotiation. This vulnerability allowed an attacker to
+"prefix" a chosen plaintext to the HTTP request as seen by the web
+server. A protocol extension was developed which fixed this
+vulnerability if supported by both client and server.
+
+If mod_ssl is linked against OpenSSL version 1.0.0
+Beta 5 or later, by default renegotiation is only supported with
+clients supporting the new protocol extension. If this directive is
+enabled, renegotiation will be allowed with old (unpatched) clients.
+SSL connections will be vulnerable to the prefix attack as described
+above if this directive is enabled. The SSL_SECURE_RENEG
+variable can be used to determine whether secure renegotiation is
+supported for a given SSL connection.
+
+Example
+SSLInsecureRenegotiation on
+
+
+
+
--
2.40.0