Am 21.02.22 um 12:19 schrieb Frank Lichtenheld:
- Fix various formatting inconsistencies
- Explain what NCP means before using it.
- Also replace some of the usages of NCP
   with the clearer "cipher negotiation".

Signed-off-by: Frank Lichtenheld <fr...@lichtenheld.com>
---
  doc/man-sections/protocol-options.rst | 34 +++++++++++++--------------
  1 file changed, 17 insertions(+), 17 deletions(-)

diff --git a/doc/man-sections/protocol-options.rst 
b/doc/man-sections/protocol-options.rst
index 1c6b1200..4af65983 100644
--- a/doc/man-sections/protocol-options.rst
+++ b/doc/man-sections/protocol-options.rst
@@ -73,7 +73,7 @@ configured in a compatible way between both the local and 
remote side.
    Starting with 2.6.0, this option is always ignored in TLS mode
    when it comes to configuring the cipher and will only control the
    cipher for ``--secret`` pre-shared-key mode (note: this mode is
-  deprecated strictly not recommended).
+  deprecated and strictly not recommended).
If you wish to specify the cipher to use on the data channel,
    please see ``--data-ciphers`` (for regular negotiation) and
@@ -87,8 +87,8 @@ configured in a compatible way between both the local and 
remote side.
    Set ``alg`` to :code:`none` to disable encryption.
--compress algorithm
-  **DEPRECATED** Enable a compression algorithm.  Compression is generally
-  not recommended.  VPN tunnels which use compression are susceptible to
+  **DEPRECATED** Enable a compression algorithm. Compression is generally
+  not recommended. VPN tunnels which use compression are susceptible to
    the VORALCE attack vector. See also the :code:`migrate` parameter below.
The ``algorithm`` parameter may be :code:`lzo`, :code:`lz4`,
@@ -191,7 +191,8 @@ configured in a compatible way between both the local and 
remote side.
For servers, the first cipher from ``cipher-list`` that is also
    supported by the client will be pushed to clients that support cipher
-  negotiation.
+  negotiation. (That feature is also called ``Negotiable crypto parameters``
+  or ``NCP`` for short).

That was actually a decision to leave out NCP out of this document. NCP is an internal thing and the documentation does not need to introduce it and can just talk about cipher negotitation in a non-specific way.

Arne



_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to