summaryrefslogtreecommitdiffstats
path: root/doc/openvpn.8
diff options
context:
space:
mode:
authorJames Yonan <james@openvpn.net>2013-06-11 00:25:05 -0600
committerDavid Sommerseth <davids@redhat.com>2013-07-15 15:59:05 +0200
commit2a92fba756d4c1e73300a12ff9e80028a6ab7c09 (patch)
treebd1a017d67319982fd8666eb3fb69ba072383a6d /doc/openvpn.8
parent4b67f9849ab3efe89268e01afddc7795f38d0f64 (diff)
downloadopenvpn-2a92fba756d4c1e73300a12ff9e80028a6ab7c09.tar.gz
openvpn-2a92fba756d4c1e73300a12ff9e80028a6ab7c09.tar.xz
openvpn-2a92fba756d4c1e73300a12ff9e80028a6ab7c09.zip
Added "setenv opt" directive prefix. If present, and if the
directive that follows is recognized, it will be processed as if the "setenv opt" prefix was absent. If present and if the directive that follows is not recognized, the directive will be ignored rather than cause a fatal error. For example, suppose you are distributing a client configuration file and want to set the minimum TLS version that the client requires from the server to 1.2. By using the following directive, setenv opt tls-version-min 1.2 or-highest only newer clients that understand the tls-version-min directive would process it, while older clients would ignore it. (cherry picked from commit 27713761e4110bb92f1c6dfe85db291e8c6e0f56) Signed-off-by: James Yonan <james@openvpn.net> URL: http://thread.gmane.org/gmane.network.openvpn.devel/7771 URL: http://thread.gmane.org/gmane.network.openvpn.devel/7744 URL: https://github.com/jamesyonan/openvpn/commit/27713761e4110bb92f1c6dfe85db291e8c6e0f56 Acked-by: Arne Schwabe <arne@rfc2549.org> Acked-by: Gert Doering <gert@greenie.muc.de> Signed-off-by: David Sommerseth <davids@redhat.com>
Diffstat (limited to 'doc/openvpn.8')
-rw-r--r--doc/openvpn.85
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/openvpn.8 b/doc/openvpn.8
index f74fe81..741f554 100644
--- a/doc/openvpn.8
+++ b/doc/openvpn.8
@@ -1891,6 +1891,11 @@ reasons for having OpenVPN fail if it detects problems in a
config file. Having said that, there are valid reasons for wanting
new software features to gracefully degrade when encountered by
older software versions.
+
+It is also possible to tag a single directive so as not to trigger
+a fatal error if the directive isn't recognized. To do this,
+prepend the following before the directive:
+.B setenv opt
.\"*********************************************************
.TP
.B \-\-setenv-safe name value