Browse code
Document that tls-crypt-v2 can be used in connection profile
As reported in https://github.com/OpenVPN/openvpn/issues/795,
tls-crypt-v2 was not documented as an option that was allowed to be used
in <connection> blocks. This is a documentation mistake - it has from
it's introduction been possible to do so.
Verified in the code and tested locally.
Github: closes OpenVPN/openvpn#795
Change-Id: Ie8c6381e66d57e0c1ec31132fad8277e0133283f
Signed-off-by: Steffan Karger <steffan@karger.me>
Gerrit URL: https://gerrit.openvpn.net/c/openvpn/+/1254
Message-Id: <20251007202816.27730-1-gert@greenie.muc.de>
URL: https://sourceforge.net/p/openvpn/mailman/message/59243550/
Signed-off-by: Gert Doering <gert@greenie.muc.de>
Steffan Karger authored on 2025/10/08 05:28:10Showing 1 changed files
| ... | ... |
@@ -58,7 +58,7 @@ block: |
| 58 | 58 |
``http-proxy-option``, ``key-direction``, ``link-mtu``, ``local``, |
| 59 | 59 |
``lport``, ``mssfix``, ``mtu-disc``, ``nobind``, ``port``, ``proto``, |
| 60 | 60 |
``remote``, ``rport``, ``socks-proxy``, ``tls-auth``, ``tls-crypt``, |
| 61 |
-``tun-mtu and``, ``tun-mtu-extra``. |
|
| 61 |
+``tls-crypt-v2``, ``tun-mtu and``, ``tun-mtu-extra``. |
|
| 62 | 62 |
|
| 63 | 63 |
A defaulting mechanism exists for specifying options to apply to all |
| 64 | 64 |
``<connection>`` profiles. If any of the above options (with the |