Skip to contentSkip to conversation

Manual page update for Re-enabled TLS version negotiation.

PATCH In review Matthias Andree 3 participants 3 messages Mar 30, 2015 – Apr 13, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Manual page update for Re-enabled TLS version negotiation.

---
 doc/openvpn.8 | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)
doc/openvpn.8 +8 -5
index a95d353..1420bdd 100644
@@ -4286,16 +4286,19 @@ include "1.0", "1.1", or "1.2".  If 'or-highest' is specified
 and version is not recognized, we will only accept the highest TLS
 version supported by the local SSL implementation.
 
-If this options is not set, the code in OpenVPN 2.3.4 will default
-to using TLS 1.0 only, without any version negotiation.  This reverts
-the beaviour to what OpenVPN versions up to 2.3.2 did, as it turned
-out that TLS version negotiation can lead to handshake problems due
-to new signature algorithms in TLS 1.2.
+Also see
+.B \-\-tls-version-max
+below, for information on compatibility.
 .\"*********************************************************
 .TP
 .B \-\-tls-version-max version
 Set the maximum TLS version we will use (default is the highest version
 supported).  Examples for version include "1.0", "1.1", or "1.2".
+
+If and only if this is set to 1.0, and OpenSSL is used (not PolarSSL),
+then OpenVPN will set up OpenSSL to use a fixed TLSv1 handshake. All
+other configurations will autonegotiate in the given limits, and the
+choice of handshake versions is left to the SSL implementation.
 .\"*********************************************************
 .TP
 .B \-\-pkcs12 file
Signature · 1 line
1.9.1
#1 lore raw

ACK

-Steffan

Quoted 35 lines · Matthias Andree
---
  doc/openvpn.8 | 13 ++++++++-----
  1 file changed, 8 insertions(+), 5 deletions(-)
doc/openvpn.8 +8 -5
index a95d353..1420bdd 100644
@@ -4286,16 +4286,19 @@ include "1.0", "1.1", or "1.2".  If 'or-highest' is specified
  and version is not recognized, we will only accept the highest TLS
  version supported by the local SSL implementation.
 
-If this options is not set, the code in OpenVPN 2.3.4 will default
-to using TLS 1.0 only, without any version negotiation.  This reverts
-the beaviour to what OpenVPN versions up to 2.3.2 did, as it turned
-out that TLS version negotiation can lead to handshake problems due
-to new signature algorithms in TLS 1.2.
+Also see
+.B \-\-tls-version-max
+below, for information on compatibility.
  .\"*********************************************************
  .TP
  .B \-\-tls-version-max version
  Set the maximum TLS version we will use (default is the highest version
  supported).  Examples for version include "1.0", "1.1", or "1.2".
+
+If and only if this is set to 1.0, and OpenSSL is used (not PolarSSL),
+then OpenVPN will set up OpenSSL to use a fixed TLSv1 handshake. All
+other configurations will autonegotiate in the given limits, and the
+choice of handshake versions is left to the SSL implementation.
  .\"*********************************************************
  .TP
  .B \-\-pkcs12 file
#2 lore raw
In reply to Matthias Andree

Your patch has been applied to the release/2.3 branch.

commit ca32c1551b05bf4cead7dceae62c412886fded55

Author: Matthias Andree
Date:   Mon Mar 30 21:54:54 2015 +0200
     Manual page update for Re-enabled TLS version negotiation.

     Signed-off-by: Matthias Andree <[email protected]...>
     Acked-by: Steffan Karger <[email protected]...>
     Message-Id: <[email protected]...>
     URL: http://article.gmane.org/gmane.network.openvpn.devel/9562
     Signed-off-by: Gert Doering <[email protected]...>

--
kind regards,

Gert Doering