Skip to contentSkip to conversation

Add section about common error with OpenVPN 2.6 and OpenSSL 3.0

PATCH Superseded Arne Schwabe 3 participants 6 messages Nov 27, 2022 – Nov 30, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Add section about common error with OpenVPN 2.6 and OpenSSL 3.0

We expect a number of configuration to no longer work with OpenVPN 2.6 and OpenSSL 3.0. This section tries to explain the most common errors that will come up and how to work around them.

---
 Changes.rst | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 84 insertions(+)
Changes.rst +84 -0
index c532d47f0..c470efa6e 100644
@@ -196,6 +196,90 @@ User-visible Changes
   software that enumerates interfaces, looking for "broadcast capable?" and
   expecting certain results.  Normal uses should not see any difference.
 
+- The default configuration will no longer allow connection to OpenVPN 2.3.x
+  or earlier, use the new ``--compat-mode`` option if you need compatibility
+  with older version. See the manual page for details.
+
+Common errors with OpenSSL 3.0 and OpenVPN 2.6
+----------------------------------------------
+Both OpenVPN 2.6 and OpenSSL 3.0 tighten the security considerable, so some
+configuration will no longer work. This section will cover the most common
+error we have seen and explain their reason and temporary workarounds. You
+should fix the problems since these workaround are not secure and will
+eventually stop working in a future update.
+
+- weak SHA1 or MD5 signature on certificates
+
+  This will happen on either loading of certificates or on connection
+  to a server::
+  
+      OpenSSL: error:0A00018E:SSL routines::ca md too weak
+      Cannot load certificate file cert.crt
+      Exiting due to fatal error
+
+  OpenSSL 3.0 no longer allows weak singatures on certificates. You can
+  downgrade your security to allow  by using ``--tls-cert-profile insecure``
+  but should replace/regenerate these certificates as soon as possible.
+
+
+- 1024 bit RSA certificates, 1024 bit DH parameters, other weak keys
+
+  This happens if you private keys or other cryptographic material that
+  does not meet today's cryptographic standards anymore. Messages are
+  similar to::
+
+      OpenSSL: error:0A00018F:SSL routines::ee key too small
+      OpenSSL: error:1408518A:SSL routines:ssl3_ctx_ctrl:dh key too small
+  
+  DH parameters (``--dh``) can be regenerated them with
+  ``openssl dhparam 2048``. For other cryptographic keys, these keys
+  and certificates need to regnerate. TLS Security level can be temporarily
+  lowered until the problem is addressed with ``tls-cert-profile legacy`` or
+  even ``tls-cert-profile insecure``.
+
+- Connecting to a OpenVPN 2.3.x server or allowing OpenVPN 2.3.x or earlier
+  clients
+
+  This will normally result in messages like::
+
+     OPTIONS ERROR: failed to negotiate cipher with server.  Add the server's cipher ('AES-128-CBC') to --data-ciphers (currently 'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this server.
+
+     or
+
+     client/127.0.0.1:49954 SENT CONTROL [client]: 'AUTH_FAILED,Data channel cipher negotiation failed (no shared cipher)' (status=1)
+
+  You can manually add the missing cipher to the ``--data-ciphers`` or use
+  the ``--compat-mode`` option. Note that these message can also indicate
+  other cipher configuration. See the data channel cipher negotiation manual
+  for more details (Available online under
+  https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/cipher-negotiation.rst)
+
+- Use of a legacy 64bit block ciphers or another deprecated cipher
+
+  OpenSSL 3.0 no longer a number of insecure and outdated ciphers. Some of
+  these cipehrs are known vulnerable (SWEET32 attack).
+
+  This will typically manifest itself in messages like::
+
+      OpenSSL: error:0308010C:digital envelope routines::unsupported
+      Cipher algorithm 'BF-CBC' not found
+      Unsupported cipher in --data-ciphers: BF-CBC
+
+  If your OpenSSL distribution comes with the legacy provider, it will allow to
+  load a legacy provider that contains the old providers. In this case you can
+  use ``--providers legacy default`` to load the legacy cipher provider.
+
+- OpenVPN version not supporting TLS 1.2 or later
+
+  The default in OpenVPN 2.6 and also in many distributions is now TLS 1.2.
+  Connecting to peer that does not support this will results in messages like::
+
+    TLS error: Unsupported protocol. This typically indicates that client and server have no common TLS version enabled. This can be caused by mismatched tls-version-min and tls-version-max options on client and server. If your OpenVPN client is between v2.3.6 and v2.3.2 try adding tls-version-min 1.0 to the client configuration to use TLS 1.0+ instead of TLS 1.0 only
+    OpenSSL: error:0A000102:SSL routines::unsupported protocol
+
+  This can be an OpenVPN 2.3.6 or earlier version. ``compat-version 2.3.0`` will
+  enable TLS 1.0 support if supported by the OpenSSL distribution. Note that
+  on some Linux distributions enabling TLS 1.1 or 1.0 is not possible.
 
 Overview of changes in 2.5
 ==========================
Signature · 1 line
2.37.1 (Apple Git-137.1)
#1 lore raw
Quoted 14 lines · Arne Schwabe

We expect a number of configuration to no longer work with OpenVPN 2.6 and OpenSSL 3.0. This section tries to explain the most common errors that will come up and how to work around them.

---
 Changes.rst | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 84 insertions(+)
Changes.rst +0 -0
index c532d47f0..c470efa6e 100644

Changes.rst User-visible Changes · line 201

Quoted 6 lines
Changes.rst +3 -0
@@ -196,6 +196,90 @@ User-visible Changes
   software that enumerates interfaces, looking for "broadcast capable?" and
   expecting certain results.  Normal uses should not see any difference.
 
+- The default configuration will no longer allow connection to OpenVPN 2.3.x
+  or earlier, use the new ``--compat-mode`` option if you need compatibility
+  with older version. See the manual page for details.

"versions"?

Changes.rst User-visible Changes · line 207

Quoted 6 lines
Changes.rst +6 -0
+
+Common errors with OpenSSL 3.0 and OpenVPN 2.6
+----------------------------------------------
+Both OpenVPN 2.6 and OpenSSL 3.0 tighten the security considerable, so some
+configuration will no longer work. This section will cover the most common
+error we have seen and explain their reason and temporary workarounds. You

"errors"
"reason" -> "cause" ?

Changes.rst User-visible Changes · line 208

Quoted 1 line
Changes.rst +1 -0
+should fix the problems since these workaround are not secure and will

"problems" -> "underlying problems as soon as possible"

Changes.rst User-visible Changes · line 221

Quoted 13 lines
Changes.rst +13 -0
+eventually stop working in a future update.
+
+- weak SHA1 or MD5 signature on certificates
+
+  This will happen on either loading of certificates or on connection
+  to a server::
+  
+      OpenSSL: error:0A00018E:SSL routines::ca md too weak
+      Cannot load certificate file cert.crt
+      Exiting due to fatal error
+
+  OpenSSL 3.0 no longer allows weak singatures on certificates. You can
+  downgrade your security to allow  by using ``--tls-cert-profile insecure``

"allow" -> "allow them"

Changes.rst User-visible Changes · line 227

Quoted 6 lines
Changes.rst +6 -0
+  but should replace/regenerate these certificates as soon as possible.
+
+
+- 1024 bit RSA certificates, 1024 bit DH parameters, other weak keys
+
+  This happens if you private keys or other cryptographic material that

"you" -> "you use"

Changes.rst User-visible Changes · line 234

Quoted 7 lines
Changes.rst +7 -0
+  does not meet today's cryptographic standards anymore. Messages are
+  similar to::
+
+      OpenSSL: error:0A00018F:SSL routines::ee key too small
+      OpenSSL: error:1408518A:SSL routines:ssl3_ctx_ctrl:dh key too small
+  
+  DH parameters (``--dh``) can be regenerated them with

remove "them"

Changes.rst User-visible Changes · line 236

Quoted 2 lines
Changes.rst +2 -0
+  ``openssl dhparam 2048``. For other cryptographic keys, these keys
+  and certificates need to regnerate. TLS Security level can be temporarily

"regnerate" -> "be regenerated". But the sentence is still bad due to the repetition of "regenerate". Don't have a good replacement, though.

Changes.rst User-visible Changes · line 237

Quoted 1 line
Changes.rst +1 -0
+  lowered until the problem is addressed with ``tls-cert-profile legacy`` or

remove "until the problem is addressed", it is implied anyway. "--tls-cert-profile" for consistency.

Quoted 5 lines
Changes.rst +5 -0
+  even ``tls-cert-profile insecure``.
+
+- Connecting to a OpenVPN 2.3.x server or allowing OpenVPN 2.3.x or earlier
+  clients
+

Changes.rst User-visible Changes · line 252

Quoted 10 lines
Changes.rst +10 -0
+  This will normally result in messages like::
+
+     OPTIONS ERROR: failed to negotiate cipher with server.  Add the server's cipher ('AES-128-CBC') to --data-ciphers (currently 'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this server.
+
+     or
+
+     client/127.0.0.1:49954 SENT CONTROL [client]: 'AUTH_FAILED,Data channel cipher negotiation failed (no shared cipher)' (status=1)
+
+  You can manually add the missing cipher to the ``--data-ciphers`` or use
+  the ``--compat-mode`` option. Note that these message can also indicate

"messages", or "this"

Changes.rst User-visible Changes · line 253

Quoted 1 line
Changes.rst +1 -0
+  other cipher configuration. See the data channel cipher negotiation manual

missing "problems"?

Changes.rst User-visible Changes · line 255

Quoted 2 lines
Changes.rst +2 -0
+  for more details (Available online under
+  https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/cipher-negotiation.rst)

Might want to use https://build.openvpn.net/man/openvpn-2.6/openvpn.8.html#data-channel-cipher-negotiation instead? Doesn't exist yet, but will be created on Alpha release.

Changes.rst User-visible Changes · line 257

Quoted 2 lines
Changes.rst +2 -0
+
+- Use of a legacy 64bit block ciphers or another deprecated cipher

"another" -> "other"
"cipher" -> "ciphers"

Changes.rst User-visible Changes · line 259

Quoted 2 lines
Changes.rst +2 -0
+
+  OpenSSL 3.0 no longer a number of insecure and outdated ciphers. Some of

missing "supports"?

Changes.rst User-visible Changes · line 260

Quoted 1 line
Changes.rst +1 -0
+  these cipehrs are known vulnerable (SWEET32 attack).

"ciphers"

Changes.rst User-visible Changes · line 269

Quoted 9 lines
Changes.rst +9 -0
+
+  This will typically manifest itself in messages like::
+
+      OpenSSL: error:0308010C:digital envelope routines::unsupported
+      Cipher algorithm 'BF-CBC' not found
+      Unsupported cipher in --data-ciphers: BF-CBC
+
+  If your OpenSSL distribution comes with the legacy provider, it will allow to
+  load a legacy provider that contains the old providers. In this case you can

"it will allow ..." -> "you can load it to enable support for the old ciphers". Remove "In this case".

Changes.rst User-visible Changes · line 275

Quoted 6 lines
Changes.rst +6 -0
+  use ``--providers legacy default`` to load the legacy cipher provider.
+
+- OpenVPN version not supporting TLS 1.2 or later
+
+  The default in OpenVPN 2.6 and also in many distributions is now TLS 1.2.
+  Connecting to peer that does not support this will results in messages like::

"a peer"

Changes.rst User-visible Changes · line 277

Quoted 2 lines
Changes.rst +2 -0
+
+    TLS error: Unsupported protocol. This typically indicates that client and server have no common TLS version enabled. This can be caused by mismatched tls-version-min and tls-version-max options on client and server. If your OpenVPN client is between v2.3.6 and v2.3.2 try adding tls-version-min 1.0 to the client configuration to use TLS 1.0+ instead of TLS 1.0 only

Line breaks?

Changes.rst User-visible Changes · line 285

Quoted 8 lines
Changes.rst +5 -0
+    OpenSSL: error:0A000102:SSL routines::unsupported protocol
+
+  This can be an OpenVPN 2.3.6 or earlier version. ``compat-version 2.3.0`` will
+  enable TLS 1.0 support if supported by the OpenSSL distribution. Note that
+  on some Linux distributions enabling TLS 1.1 or 1.0 is not possible.
 
 Overview of changes in 2.5
 ==========================

Regards,

Signature · 1 line
  Frank Lichtenheld
#2 lore raw
Quoted 7 lines

Changes.rst User-visible Changes · line 255

Quoted 4 lines
Changes.rst +2 -0
+  for more details (Available online under
+  https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/cipher-negotiation.rst)

Might want to use https://build.openvpn.net/man/openvpn-2.6/openvpn.8.html#data-channel-cipher-negotiation instead? Doesn't exist yet, but will be created on Alpha release.

Hm yes. The rendering on the 2.5 page is very barebone, the github version looks actually a lot better. I would keep it this way for now and after branching of the 2.6 branch we update both references of github.com in this document to manual section to fixed 2.6 links

Quoted 37 lines
Quoted 2 lines

+
+- Use of a legacy 64bit block ciphers or another deprecated cipher

"another" -> "other"
"cipher" -> "ciphers"

Review

Quoted 2 lines
(quoted diff) +2 -0
+
+  OpenSSL 3.0 no longer a number of insecure and outdated ciphers. Some of

missing "supports"?

Quoted 1 line

+ these cipehrs are known vulnerable (SWEET32 attack).

"ciphers"

Changes.rst User-visible Changes · line 269

Quoted 9 lines
Changes.rst +9 -0
+
+  This will typically manifest itself in messages like::
+
+      OpenSSL: error:0308010C:digital envelope routines::unsupported
+      Cipher algorithm 'BF-CBC' not found
+      Unsupported cipher in --data-ciphers: BF-CBC
+
+  If your OpenSSL distribution comes with the legacy provider, it will allow to
+  load a legacy provider that contains the old providers. In this case you can

"it will allow ..." -> "you can load it to enable support for the old ciphers". Remove "In this case".

Changes.rst User-visible Changes · line 275

Quoted 6 lines
Changes.rst +6 -0
+  use ``--providers legacy default`` to load the legacy cipher provider.
+
+- OpenVPN version not supporting TLS 1.2 or later
+
+  The default in OpenVPN 2.6 and also in many distributions is now TLS 1.2.
+  Connecting to peer that does not support this will results in messages like::

"a peer"

Quoted 4 lines

Review

Quoted 2 lines
(quoted diff) +2 -0
+
+    TLS error: Unsupported protocol. This typically indicates that client and server have no common TLS version enabled. This can be caused by mismatched tls-version-min and tls-version-max options on client and server. If your OpenVPN client is between v2.3.6 and v2.3.2 try adding tls-version-min 1.0 to the client configuration to use TLS 1.0+ instead of TLS 1.0 only

Line breaks?

Good question. The original message does not have any. I will break it up into multiple lines for the next patch version.

Arne

#3 lore raw

PATCH v2 1/1 Add section about common error with OpenVPN 2.6 and OpenSSL 3.0

In reply to Arne Schwabe

We expect a number of configuration to no longer work with OpenVPN 2.6 and OpenSSL 3.0. This section tries to explain the most common errors that will come up and how to work around them.

Patch V2: several mistakes highlighed and suggestions made by Frank
included.

---
 Changes.rst | 93 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 93 insertions(+)
Changes.rst +93 -0
index f316115f3..39d43a7f4 100644
@@ -190,6 +190,99 @@ User-visible Changes
   software that enumerates interfaces, looking for "broadcast capable?" and
   expecting certain results.  Normal uses should not see any difference.
 
+- The default configuration will no longer allow connections to OpenVPN 2.3.x
+  peer or earlier, use the new ``--compat-mode`` option if you need
+  compatibility with older versions. See the manual page on the
+  ``--compat-mode`` for details.
+
+Common errors with OpenSSL 3.0 and OpenVPN 2.6
+----------------------------------------------
+Both OpenVPN 2.6 and OpenSSL 3.0 tighten the security considerable, so some
+configuration will no longer work. This section will cover the most common
+causes and error message we have seen and explain their reason and temporary
+workarounds. You should fix the underlying problems as soon as possible since
+these workaround are not secure and will eventually stop working in a future
+update.
+
+- weak SHA1 or MD5 signature on certificates
+
+  This will happen on either loading of certificates or on connection
+  to a server::
+  
+      OpenSSL: error:0A00018E:SSL routines::ca md too weak
+      Cannot load certificate file cert.crt
+      Exiting due to fatal error
+
+  OpenSSL 3.0 no longer allows weak signatures on certificates. You can
+  downgrade your security to allow them by using ``--tls-cert-profile insecure``
+  but should replace/regenerate these certificates as soon as possible.
+
+
+- 1024 bit RSA certificates, 1024 bit DH parameters, other weak keys
+
+  This happens if you use private keys or other cryptographic material that
+  does not meet today's cryptographic standards anymore. Messages are similar
+  to::
+
+      OpenSSL: error:0A00018F:SSL routines::ee key too small
+      OpenSSL: error:1408518A:SSL routines:ssl3_ctx_ctrl:dh key too small
+  
+  DH parameters (``--dh``) can be regenerated with ``openssl dhparam 2048``.
+  For other cryptographic keys, these keys and certificates need to be
+  regenerated. TLS Security level can be temporarily lowered with
+  ``--tls-cert-profile legacy`` or even ``--tls-cert-profile insecure``.
+
+- Connecting to a OpenVPN 2.3.x server or allowing OpenVPN 2.3.x or earlier
+  clients
+
+  This will normally result in messages like::
+
+     OPTIONS ERROR: failed to negotiate cipher with server.  Add the server's cipher ('AES-128-CBC') to --data-ciphers (currently 'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this server.
+
+     or
+
+     client/127.0.0.1:49954 SENT CONTROL [client]: 'AUTH_FAILED,Data channel cipher negotiation failed (no shared cipher)' (status=1)
+
+  You can manually add the missing cipher to the ``--data-ciphers``. The
+  standard ciphers should be included as well, e.g.
+  ``--data-ciphers AES-256-GCM:AES-128-GCM:?Chacha20-Poly1305:?AES-128-CBC``.
+  You can also use the ``--compat-mode`` option. Note that these message may
+  also indicate other cipher configuration problems. See the data channel
+  cipher negotiation manual section for more details. (Available online under
+  https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/cipher-negotiation.rst)
+
+- Use of a legacy or deprecated cipher (e.g. 64bit block ciphers)
+
+  OpenSSL 3.0 no longer supports a number of insecure and outdated ciphers in
+  its default configuration. Some of these ciphers are known to be vulnerable (SWEET32 attack).
+
+  This will typically manifest itself in messages like::
+
+      OpenSSL: error:0308010C:digital envelope routines::unsupported
+      Cipher algorithm 'BF-CBC' not found
+      Unsupported cipher in --data-ciphers: BF-CBC
+
+  If your OpenSSL distribution comes with the legacy provider (see
+  also ``man OSSL_PROVIDER-legacy``), you can load the OpenSSL legacy provider
+  that contains the old algorithms. Use ``--providers legacy default`` to load
+  the OpenSSL legacy provider.
+
+- OpenVPN version not supporting TLS 1.2 or later
+
+  The default in OpenVPN 2.6 and also in many distributions is now TLS 1.2 or
+  later. Connecting to a peer that does not support this will results in
+  messages like::
+
+    TLS error: Unsupported protocol. This typically indicates that client and
+    server have no common TLS version enabled. This can be caused by mismatched
+    tls-version-min and tls-version-max options on client and server. If your
+    OpenVPN client is between v2.3.6 and v2.3.2 try adding tls-version-min 1.0
+    to the client configuration to use TLS 1.0+ instead of TLS 1.0 only
+    OpenSSL: error:0A000102:SSL routines::unsupported protocol
+
+  This can be an OpenVPN 2.3.6 or earlier version. ``compat-version 2.3.0`` will
+  enable TLS 1.0 support if supported by the OpenSSL distribution. Note that
+  on some Linux distributions enabling TLS 1.1 or 1.0 is not possible.
 
 Overview of changes in 2.5
 ==========================
Signature · 1 line
2.37.1 (Apple Git-137.1)
Acked-by on v2 1/1
#4 lore raw

Still a few small suggestions. See below. But generally

Quoted 1 line · Arne Schwabe

We expect a number of configuration to no longer work with OpenVPN

"configurations"

Quoted 18 lines

2.6 and OpenSSL 3.0. This section tries to explain the most common errors that will come up and how to work around them.

Patch V2: several mistakes highlighed and suggestions made by Frank
included.

---
 Changes.rst | 93 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 93 insertions(+)
Changes.rst +0 -0
index f316115f3..39d43a7f4 100644
@@ -190,6 +190,99 @@ User-visible Changes
   software that enumerates interfaces, looking for "broadcast capable?" and
   expecting certain results.  Normal uses should not see any difference.

Changes.rst User-visible Changes · line 201

Quoted 10 lines
Changes.rst +9 -0
 
+- The default configuration will no longer allow connections to OpenVPN 2.3.x
+  peer or earlier, use the new ``--compat-mode`` option if you need
+  compatibility with older versions. See the manual page on the
+  ``--compat-mode`` for details.
+
+Common errors with OpenSSL 3.0 and OpenVPN 2.6
+----------------------------------------------
+Both OpenVPN 2.6 and OpenSSL 3.0 tighten the security considerable, so some
+configuration will no longer work. This section will cover the most common

"configurations"

Quoted 57 lines
Changes.rst +57 -0
+causes and error message we have seen and explain their reason and temporary
+workarounds. You should fix the underlying problems as soon as possible since
+these workaround are not secure and will eventually stop working in a future
+update.
+
+- weak SHA1 or MD5 signature on certificates
+
+  This will happen on either loading of certificates or on connection
+  to a server::
+  
+      OpenSSL: error:0A00018E:SSL routines::ca md too weak
+      Cannot load certificate file cert.crt
+      Exiting due to fatal error
+
+  OpenSSL 3.0 no longer allows weak signatures on certificates. You can
+  downgrade your security to allow them by using ``--tls-cert-profile insecure``
+  but should replace/regenerate these certificates as soon as possible.
+
+
+- 1024 bit RSA certificates, 1024 bit DH parameters, other weak keys
+
+  This happens if you use private keys or other cryptographic material that
+  does not meet today's cryptographic standards anymore. Messages are similar
+  to::
+
+      OpenSSL: error:0A00018F:SSL routines::ee key too small
+      OpenSSL: error:1408518A:SSL routines:ssl3_ctx_ctrl:dh key too small
+  
+  DH parameters (``--dh``) can be regenerated with ``openssl dhparam 2048``.
+  For other cryptographic keys, these keys and certificates need to be
+  regenerated. TLS Security level can be temporarily lowered with
+  ``--tls-cert-profile legacy`` or even ``--tls-cert-profile insecure``.
+
+- Connecting to a OpenVPN 2.3.x server or allowing OpenVPN 2.3.x or earlier
+  clients
+
+  This will normally result in messages like::
+
+     OPTIONS ERROR: failed to negotiate cipher with server.  Add the server's cipher ('AES-128-CBC') to --data-ciphers (currently 'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this server.
+
+     or
+
+     client/127.0.0.1:49954 SENT CONTROL [client]: 'AUTH_FAILED,Data channel cipher negotiation failed (no shared cipher)' (status=1)
+
+  You can manually add the missing cipher to the ``--data-ciphers``. The
+  standard ciphers should be included as well, e.g.
+  ``--data-ciphers AES-256-GCM:AES-128-GCM:?Chacha20-Poly1305:?AES-128-CBC``.
+  You can also use the ``--compat-mode`` option. Note that these message may
+  also indicate other cipher configuration problems. See the data channel
+  cipher negotiation manual section for more details. (Available online under
+  https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/cipher-negotiation.rst)
+
+- Use of a legacy or deprecated cipher (e.g. 64bit block ciphers)
+
+  OpenSSL 3.0 no longer supports a number of insecure and outdated ciphers in
+  its default configuration. Some of these ciphers are known to be vulnerable (SWEET32 attack).
+

Changes.rst User-visible Changes · line 268

Quoted 10 lines
Changes.rst +10 -0
+  This will typically manifest itself in messages like::
+
+      OpenSSL: error:0308010C:digital envelope routines::unsupported
+      Cipher algorithm 'BF-CBC' not found
+      Unsupported cipher in --data-ciphers: BF-CBC
+
+  If your OpenSSL distribution comes with the legacy provider (see
+  also ``man OSSL_PROVIDER-legacy``), you can load the OpenSSL legacy provider
+  that contains the old algorithms. Use ``--providers legacy default`` to load
+  the OpenSSL legacy provider.

Much redundancy. Maybe

"If your OpenSSL distribution comes with the legacy provider (see
also ``man OSSL_PROVIDER-legacy``), you can load it with ``--providers legacy default``. This will re-enable the old algorithms."

Quoted 10 lines
Changes.rst +10 -0
+
+- OpenVPN version not supporting TLS 1.2 or later
+
+  The default in OpenVPN 2.6 and also in many distributions is now TLS 1.2 or
+  later. Connecting to a peer that does not support this will results in
+  messages like::
+
+    TLS error: Unsupported protocol. This typically indicates that client and
+    server have no common TLS version enabled. This can be caused by mismatched
+    tls-version-min and tls-version-max options on client and server. If your

Changes.rst User-visible Changes · line 288

Quoted 10 lines
Changes.rst +7 -0
+    OpenVPN client is between v2.3.6 and v2.3.2 try adding tls-version-min 1.0
+    to the client configuration to use TLS 1.0+ instead of TLS 1.0 only
+    OpenSSL: error:0A000102:SSL routines::unsupported protocol
+
+  This can be an OpenVPN 2.3.6 or earlier version. ``compat-version 2.3.0`` will
+  enable TLS 1.0 support if supported by the OpenSSL distribution. Note that
+  on some Linux distributions enabling TLS 1.1 or 1.0 is not possible.
 
 Overview of changes in 2.5
 ==========================

Regards,

Signature · 1 line
  Frank Lichtenheld
#5 lore raw
In reply to Arne Schwabe

Your patch has been applied to the master branch.

configuration*s* and legacy providers adjusted as instructed.

Arne, thanks a lot for this (Berni was also waiting for something like this, to include in their release notes).

commit 2b62fc7ff5018e252e49ad01c4b9720fa2fa6200

Author: Arne Schwabe
Date:   Tue Nov 29 12:30:31 2022 +0100
     Add section about common error with OpenVPN 2.6 and OpenSSL 3.0

     Signed-off-by: Arne Schwabe <[email protected]...>
     Acked-by: Frank Lichtenheld <[email protected]...>
     Message-Id: <[email protected]...>
     URL: https://www.mail-archive.com/[email protected]/msg25571.html
     Signed-off-by: Gert Doering <[email protected]...>

--
kind regards,

Gert Doering