Changes between Version 12 and Version 13 of Openvpn23ManPage

Timestamp:

10/28/14 18:13:46 (9 years ago)

Author:

Samuli Seppänen

Comment:

Updated man-page to 2.3.5

Openvpn23ManPage

@@ -1975 +1975 @@
 <P>
 The server timeout is set twice the value of the second argument.
-This ensures that a timeout is dectected on client side
+This ensures that a timeout is detected on client side
 before the server side drops the connection.
 <P>
@@ -3027 +3027 @@
 <P>
 Adaptive compression tries to optimize the case where you have
-compression enabled, but you are sending predominantly uncompressible
+compression enabled, but you are sending predominantly incompressible
 (or pre-compressed) packets over the tunnel, such as an FTP or rsync transfer
 of a large, compressed file.  With adaptive compression,
@@ -3274 +3274 @@
 
 <DL COMPACT>
-<DT><B>--server network netmask</B>
+<DT><B>--server network netmask ['nopool']</B>
 
 <DD>
@@ -3310 +3310 @@
      ifconfig-pool 10.8.0.2 10.8.0.254 255.255.255.0
    push &quot;route-gateway 10.8.0.1&quot;
+   if route-gateway unset:
+     route-gateway 10.8.0.2
+
 </B></PRE>
 
@@ -4273 +4276 @@
 
 <DT><DD>
-In addition the old behavivour was to remap any character other than
+In addition the old behaviour was to remap any character other than
 alphanumeric, underscore ('_'), dash ('-'), dot ('.'), and slash ('/') to
 underscore ('_').  The X.509 Subject string as returned by the
@@ -5299 +5302 @@
 <B>0</B>
 
-(default) -- Try to determind automatically.
+(default) -- Try to determine automatically.
 <BR>
 
@@ -5771 +5774 @@
 is available via the peer_cert environment variable.
 
-<DT><B>--x509-username-field fieldname</B>
-
-<DD>
-Field in x509 certificate subject to be used as username (default=CN).
-<B>Fieldname</B>
-
-will be uppercased before matching. When this option is used, the
-<B>--verify-x509-username</B>
-
-option will match against the chosen fieldname instead of the CN.
+<DT><B>--x509-username-field [ext:]fieldname</B>
+
+<DD>
+Field in the X.509 certificate subject to be used as the username (default=CN).
+Typically, this option is specified with
+<B>fieldname</B>
+
+as either of the following:
+<P>
+<B>--x509-username-field</B>
+
+emailAddress
+<BR>
+
+<B>--x509-username-field ext:</B>subjectAltName
+
+<P>
+The first example uses the value of the &quot;emailAddress&quot; attribute in the
+certificate's Subject field as the username.  The second example uses
+the
+<B>ext:</B>
+
+prefix to signify that the X.509 extension
+<B>fieldname</B>
+
+&quot;subjectAltName&quot; be searched for an rfc822Name (email) field to be used
+as the username.  In cases where there are multiple email addresses
+in
+<B>ext:fieldname</B>,
+
+the last occurrence is chosen.
+<P>
+When this option is used, the
+<B>--verify-x509-name</B>
+
+option will match against the chosen
+<B>fieldname</B>
+
+instead of the Common Name.
+<P>
+<B>Please note:</B>
+
+This option has a feature which will convert an all-lowercase
+<B>fieldname</B>
+
+to uppercase characters, e.g., ou -&gt; OU.  A mixed-case
+<B>fieldname</B>
+
+or one having the
+<B>ext:</B>
+
+prefix will be left as-is.  This automatic upcasing feature
+is deprecated and will be removed in a future release.
 
 <DT><B>--tls-remote name (DEPRECATED)</B>
@@ -8311 +8357 @@
 <A HREF="/cgi-bin/man/man2html">man2html</A>,
 using the manual pages.<BR>
-Time: 07:38:58 GMT, May 06, 2014
+Time: 18:09:54 GMT, October 28, 2014
 }}}