[Openvpn-devel,2/2] doc: fix typos in cipher-negotiation.rst
Commit Message
Signed-off-by: Magnus Kroken <mkroken@gmail.com>
---
doc/man-sections/cipher-negotiation.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Comments
Your patch has been applied to the master and release/2.5 branch.
commit e33f44754a5f81ea013070dba3cdc162f41d1257 (master)
commit 4764868240ed215c91de659c742c393ebb602eeb (release/2.5)
Author: Magnus Kroken
Date: Sat Aug 15 14:05:22 2020 +0200
doc: fix typos in cipher-negotiation.rst
Signed-off-by: Magnus Kroken <mkroken@gmail.com>
Acked-by: Gert Doering <gert@greenie.muc.de>
Message-Id: <20200815120522.1404-3-mkroken@gmail.com>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg20748.html
Signed-off-by: Gert Doering <gert@greenie.muc.de>
--
kind regards,
Gert Doering
@@ -38,7 +38,7 @@ options to avoid this behaviour.
OpenVPN 3 clients
-----------------
Clients based on the OpenVPN 3.x library (https://github.com/openvpn/openvpn3/)
-do not have a configurable ``--ncp-ciphers`` or ``--data-cipher`` option. Instead
+do not have a configurable ``--ncp-ciphers`` or ``--data-ciphers`` option. Instead
these clients will announce support for all their supported AEAD ciphers
(`AES-256-GCM`, `AES-128-GCM` and in newer versions also `Chacha20-Poly1305`).
@@ -90,7 +90,7 @@ version. The default was never changed to ensure backwards compatibility.
In OpenVPN 2.5 this behaviour has now been changed so that if the ``--cipher``
is not explicitly set it does not allow the weak ``BF-CBC`` cipher any more
and needs to explicitly added as ``--cipher BFC-CBC`` or added to
-``-data-ciphers``.
+``--data-ciphers``.
We strongly recommend to switching away from BF-CBC to a
more secure cipher as soon as possible instead.