From 2d75e9aad3c1ef11c38c41d118fb5ae753a95ae4 Mon Sep 17 00:00:00 2001 From: Dimitri Papadopoulos <3234522+DimitriPapadopoulos@users.noreply.github.com> Date: Mon, 4 Mar 2024 14:18:59 +0100 Subject: [PATCH] Add the new `tun` option to the documentation --- doc/openfortivpn.1.in | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/openfortivpn.1.in b/doc/openfortivpn.1.in index 62e2ad1d..8f6a8a0a 100644 --- a/doc/openfortivpn.1.in +++ b/doc/openfortivpn.1.in @@ -16,6 +16,7 @@ openfortivpn \- Client for PPP+TLS VPN tunnel services [\fB\-\-otp\-delay=\fI\fR] [\fB\-\-no\-ftm\-push\fR] [\fB\-\-realm=\fI\fR] +[\fB\-\-tun=\fI\fR] [\fB\-\-ifname=\fI\fR] [\fB\-\-set\-routes=\fI\fR] [\fB\-\-no\-routes\fR] @@ -106,6 +107,9 @@ authentication based on OTP will be used instead. Connect to the specified authentication realm. Defaults to empty, which is usually what you want. .TP +\fB\-\-tun=\fI\fR +Set to create a TUN device and use internal PPP code (experimental). +.TP \fB\-\-ifname=\fI\fR Bind the connection to the specified network interface. .TP @@ -182,9 +186,9 @@ OpenSSL ciphers to use. If default does not work, you can try alternatives such as HIGH:!MD5:!RC4 or as suggested by the Cipher: line in the output of \fBopenssl\fP(1) (e.g. AES256-GCM-SHA384): -$ openssl s_client -connect \fI\fR + $ openssl s_client -connect \fI\fR -(default: HIGH:!aNULL:!kRSA:!PSK:!SRP:!MD5:!RC4) + (default: HIGH:!aNULL:!kRSA:!PSK:!SRP:!MD5:!RC4) \fBApplies to TLS v1.2 or lower only, not to be used with TLS v1.3 ciphers.\fR .TP