<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>OpenConnect VPN client.</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="description" content="VPN client compatible with Cisco AnyConnect SSL VPN" />
<meta name="keywords" content="OpenConnect, AnyConnect, Cisco, VPN, SSLVPN, SSL VPN" />
<link href="./styles/main.css" rel="styleSheet" type="text/css" />
<link href='http://fonts.googleapis.com/css?family=Raleway' rel='stylesheet' type='text/css' />
</head>
<body>
<div id="logo" align="right">
<img src="./images/openconnect.png" height="96px" alt="OpenConnect" />
</div>
<div id="main">
<div id="menu1">
<span class="nonsel">
<a href="index.html"><span>Home</span></a>
</span>
<span class="nonsel">
<a href="features.html"><span>Features</span></a>
</span>
<span class="sel">
<a href="building.html"><span>Getting Started</span></a>
</span>
<span class="nonsel">
<a href="mail.html"><span>Mailing List / Help</span></a>
</span>
<span class="nonsel">
<a href="contribute.html"><span>Contribute</span></a>
</span>
<span class="nonsel">
<a href="anyconnect.html"><span>Protocols</span></a>
</span>
<span class="nonsel">
<a href="http://www.infradead.org/ocserv/"><span>VPN Server</span></a>
</span>
<p>OpenConnect VPN client</p>
</div>
<div id="menu2">
<span class="nonsel">
<a href="building.html"><span>Building</span></a>
</span>
<span class="nonsel">
<a href="vpnc-script.html"><span>vpnc-script</span></a>
</span>
<span class="nonsel">
<a href="connecting.html"><span>Connecting</span></a>
</span>
<span class="sel">
<a href="manual.html"><span>Manual</span></a>
</span>
</div>
<div id="textbox">
<div id="text">
</div>
<h1>OPENCONNECT</h1>
<p><a href="#heading1">NAME</a><br/>
<a href="#heading2">SYNOPSIS</a><br/>
<a href="#heading3">DESCRIPTION</a><br/>
<a href="#heading4">OPTIONS</a><br/>
<a href="#heading5">SIGNALS</a><br/>
<a href="#heading6">LIMITATIONS</a><br/>
<a href="#heading7">AUTHORS</a><br/>
</p>
<hr/>
<h2 id="heading1">NAME
</h2>
<p style="margin-left:11%; margin-top: 1em">openconnect
- Connect to Cisco AnyConnect VPN</p>
<h2 id="heading2">SYNOPSIS
</h2>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<colgroup><col width="11%"></col>
<col width="17%"></col>
<col width="1%" class="center"></col>
<col width="71%"></col>
</colgroup>
<tr valign="top" align="left">
<td></td>
<td>
<p style="margin-top: 1em"><b>openconnect</b></p></td>
<td></td>
<td>
<p style="margin-top: 1em">[<b>--config </b><i>configfile</i>]
[<b>-b,--background</b>]
[<b>--pid-file </b><i>pidfile</i>]
[<b>-c,--certificate </b><i>cert</i>]
[<b>-e,--cert-expire-warning </b><i>days</i>]
[<b>-k,--sslkey </b><i>key</i>]
[<b>-C,--cookie </b><i>cookie</i>]
[<b>--cookie-on-stdin</b>]
[<b>--compression </b><i>MODE</i>]
[<b>-d,--deflate</b>]
[<b>-D,--no-deflate</b>]
[<b>--force-dpd </b><i>interval</i>]
[<b>-g,--usergroup </b><i>group</i>]
[<b>-h,--help</b>]
[<b>--http-auth </b><i>methods</i>]
[<b>-i,--interface </b><i>ifname</i>]
[<b>-l,--syslog</b>]
[<b>--timestamp</b>]
[<b>--passtos</b>]
[<b>-U,--setuid </b><i>user</i>]
[<b>--csd-user </b><i>user</i>]
[<b>-m,--mtu </b><i>mtu</i>]
[<b>--base-mtu </b><i>mtu</i>]
[<b>-p,--key-password </b><i>pass</i>]
[<b>-P,--proxy </b><i>proxyurl</i>]
[<b>--proxy-auth </b><i>methods</i>]
[<b>--no-proxy</b>]
[<b>--libproxy</b>]
[<b>--key-password-from-fsid</b>]
[<b>-q,--quiet</b>]
[<b>-Q,--queue-len </b><i>len</i>]
[<b>-s,--script </b><i>vpnc-script</i>]
[<b>-S,--script-tun</b>]
[<b>-u,--user </b><i>name</i>]
[<b>-V,--version</b>]
[<b>-v,--verbose</b>]
[<b>-x,--xmlconfig </b><i>config</i>]
[<b>--authgroup </b><i>group</i>]
[<b>--authenticate</b>]
[<b>--cookieonly</b>]
[<b>--printcookie</b>]
[<b>--cafile </b><i>file</i>]
[<b>--disable-ipv6</b>]
[<b>--dtls-ciphers </b><i>list</i>]
[<b>--dtls-local-port </b><i>port</i>]
[<b>--dump-http-traffic</b>]
[<b>--no-system-trust</b>]
[<b>--pfs</b>]
[<b>--no-dtls</b>]
[<b>--no-http-keepalive</b>]
[<b>--no-passwd</b>]
[<b>--no-xmlpost</b>]
[<b>--non-inter</b>]
[<b>--passwd-on-stdin</b>]
[<b>--protocol </b><i>proto</i>]
[<b>--token-mode </b><i>mode</i>]
[<b>--token-secret </b><i>{secret</i>[<i>,counter</i>]|@<i>file</i>}]
[<b>--reconnect-timeout</b>]
[<b>--resolve </b><i>host:ip</i>]
[<b>--servercert </b><i>sha1</i>]
[<b>--useragent </b><i>string</i>]
[<b>--local-hostname </b><i>string</i>]
[<b>--os </b><i>string</i>]
<b>[https://]</b><i>server</i><b>[:</b><i>port</i><b>][/</b><i>group</i><b>]</b></p> </td></tr>
</table>
<h2 id="heading3">DESCRIPTION
</h2>
<p style="margin-left:11%; margin-top: 1em">The program
<b>openconnect</b> connects to Cisco "AnyConnect"
VPN servers, which use standard TLS and DTLS protocols for
data transport.</p>
<p style="margin-left:11%; margin-top: 1em">The connection
happens in two phases. First there is a simple HTTPS
connection over which the user authenticates somehow -
by using a certificate, or password or SecurID, etc. Having
authenticated, the user is rewarded with an HTTP cookie
which can be used to make the real VPN connection.</p>
<p style="margin-left:11%; margin-top: 1em">The second
phase uses that cookie in an HTTPS <i>CONNECT</i> request,
and data packets can be passed over the resulting
connection. In auxiliary headers exchanged with the
<i>CONNECT</i> request, a Session-ID and Master Secret
for a DTLS connection are also exchanged, which allows data
transport over UDP to occur.</p>
<h2 id="heading4">OPTIONS
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>--config=CONFIGFILE</b></p>
<p style="margin-left:22%;">Read further options from
<i>CONFIGFILE</i> before continuing to process options from
the command line. The file should contain long-format
options as would be accepted on the command line, but
without the two leading -- dashes. Empty lines,
or lines where the first non-space character is a #
character, are ignored.</p>
<p style="margin-left:22%; margin-top: 1em">Any option
except the <b>config</b> option may be specified in the
file.</p>
<p style="margin-left:11%;"><b>-b,--background</b></p>
<p style="margin-left:22%;">Continue in background after
startup</p>
<p style="margin-left:11%;"><b>--pid-file=PIDFILE</b></p>
<p style="margin-left:22%;">Save the pid to <i>PIDFILE</i>
when backgrounding</p>
<p style="margin-left:11%;"><b>-c,--certificate=CERT</b></p>
<p style="margin-left:22%;">Use SSL client certificate
<i>CERT</i> which may be either a file name or, if
OpenConnect has been built with an appropriate version of
GnuTLS, a PKCS#11 URL.</p>
<p style="margin-left:11%;"><b>-e,--cert-expire-warning=DAYS</b></p>
<p style="margin-left:22%;">Give a warning when SSL client
certificate has <i>DAYS</i> left before expiry</p>
<p style="margin-left:11%;"><b>-k,--sslkey=KEY</b></p>
<p style="margin-left:22%;">Use SSL private key <i>KEY</i>
which may be either a file name or, if OpenConnect has been
built with an appropriate version of GnuTLS, a PKCS#11
URL.</p>
<p style="margin-left:11%;"><b>-C,--cookie=COOKIE</b></p>
<p style="margin-left:22%;">Use WebVPN cookie.
<i>COOKIE</i></p>
<p style="margin-left:11%;"><b>--cookie-on-stdin</b></p>
<p style="margin-left:22%;">Read cookie from standard
input.</p>
<p style="margin-left:11%;"><b>-d,--deflate</b></p>
<p style="margin-left:22%;">Enable all compression,
including stateful modes. By default, only stateless
compression algorithms are enabled.</p>
<p style="margin-left:11%;"><b>-D,--no-deflate</b></p>
<p style="margin-left:22%;">Disable all compression.</p>
<p style="margin-left:11%;"><b>--compression=MODE</b></p>
<p style="margin-left:22%;">Set compression mode, where
<i>MODE</i> is one of <i>stateless</i> , <i>none</i> , or
<i>all .</i></p>
<p style="margin-left:22%; margin-top: 1em">By default,
only stateless compression algorithms which do not maintain
state from one packet to the next (and which can be used on
UDP transports) are enabled. By setting the mode to
<i>all</i> stateful algorithms (currently only zlib deflate)
can be enabled. Or all compression can be disabled by
setting the mode to <i>none .</i></p>
<p style="margin-left:11%;"><b>--force-dpd=INTERVAL</b></p>
<p style="margin-left:22%;">Use <i>INTERVAL</i> as minimum
Dead Peer Detection interval for CSTP and DTLS, forcing use
of DPD even when the server doesn’t request it.</p>
<p style="margin-left:11%;"><b>-g,--usergroup=GROUP</b></p>
<p style="margin-left:22%;">Use <i>GROUP</i> as login
UserGroup</p>
<p style="margin-left:11%;"><b>-h,--help</b></p>
<p style="margin-left:22%;">Display help text</p>
<p style="margin-left:11%;"><b>--http-auth=METHODS</b></p>
<p style="margin-left:22%;">Use only the specified methods
for HTTP authentication to a server. By default, only
Negotiate, NTLM and Digest authentication are enabled. Basic
authentication is also supported but because it is insecure
it must be explicitly enabled. The argument is a
comma-separated list of methods to be enabled. Note that the
order does not matter: OpenConnect will use Negotiate, NTLM,
Digest and Basic authentication in that order, if each is
enabled, regardless of the order specified in the METHODS
string.</p>
<p style="margin-left:11%;"><b>-i,--interface=IFNAME</b></p>
<p style="margin-left:22%;">Use <i>IFNAME</i> for tunnel
interface</p>
<p style="margin-left:11%;"><b>-l,--syslog</b></p>
<p style="margin-left:22%;">Use syslog for progress
messages</p>
<p style="margin-left:11%;"><b>--timestamp</b></p>
<p style="margin-left:22%;">Prepend a timestamp to each
progress message</p>
<p style="margin-left:11%;"><b>--passtos</b></p>
<p style="margin-left:22%;">Copy TOS / TCLASS of payload
packet into DTLS packets.</p>
<p style="margin-left:11%;"><b>-U,--setuid=USER</b></p>
<p style="margin-left:22%;">Drop privileges after
connecting, to become user <i>USER</i></p>
<p style="margin-left:11%;"><b>--csd-user=USER</b></p>
<p style="margin-left:22%;">Drop privileges during CSD
(Cisco Secure Desktop) script execution.</p>
<p style="margin-left:11%;"><b>--csd-wrapper=SCRIPT</b></p>
<p style="margin-left:22%;">Run <i>SCRIPT</i> instead of
the CSD (Cisco Secure Desktop) script.</p>
<p style="margin-left:11%;"><b>-m,--mtu=MTU</b></p>
<p style="margin-left:22%;">Request <i>MTU</i> from server
as the MTU of the tunnel.</p>
<p style="margin-left:11%;"><b>--base-mtu=MTU</b></p>
<p style="margin-left:22%;">Indicate <i>MTU</i> as the path
MTU between client and server on the unencrypted network.
Newer servers will automatically calculate the MTU to be
used on the tunnel from this value.</p>
<p style="margin-left:11%;"><b>-p,--key-password=PASS</b></p>
<p style="margin-left:22%;">Provide passphrase for
certificate file, or SRK (System Root Key) PIN for TPM</p>
<p style="margin-left:11%;"><b>-P,--proxy=PROXYURL</b></p>
<p style="margin-left:22%;">Use HTTP or SOCKS proxy for
connection. A username and password can be provided in the
given URL, and will be used for authentication. If
authentication is required but no credentials are given,
GSSAPI and automatic NTLM authentication using Samba’s
ntlm_auth helper tool may be attempted.</p>
<p style="margin-left:11%;"><b>--proxy-auth=METHODS</b></p>
<p style="margin-left:22%;">Use only the specified methods
for HTTP authentication to a proxy. By default, only
Negotiate, NTLM and Digest authentication are enabled. Basic
authentication is also supported but because it is insecure
it must be explicitly enabled. The argument is a
comma-separated list of methods to be enabled. Note that the
order does not matter: OpenConnect will use Negotiate, NTLM,
Digest and Basic authentication in that order, if each is
enabled, regardless of the order specified in the METHODS
string.</p>
<p style="margin-left:11%;"><b>--no-proxy</b></p>
<p style="margin-left:22%;">Disable use of proxy</p>
<p style="margin-left:11%;"><b>--libproxy</b></p>
<p style="margin-left:22%;">Use libproxy to configure proxy
automatically (when built with libproxy support)</p>
<p style="margin-left:11%;"><b>--key-password-from-fsid</b></p>
<p style="margin-left:22%;">Passphrase for certificate file
is automatically generated from the <i>fsid</i> of the file
system on which it is stored. The <i>fsid</i> is obtained
from the <b>statvfs</b>(2) or <b>statfs</b>(2) system call,
depending on the operating system. On a Linux or similar
system with GNU coreutils, the <i>fsid</i> used by this
option should be equal to the output of the command:</p>
<pre style="margin-left:22%;">stat --file-system --printf=%i\\n $CERTIFICATE</pre>
<p style="margin-left:22%;">It is not the same as the
128-bit UUID of the file system.</p>
<p style="margin-left:11%;"><b>-q,--quiet</b></p>
<p style="margin-left:22%;">Less output</p>
<p style="margin-left:11%;"><b>-Q,--queue-len=LEN</b></p>
<p style="margin-left:22%;">Set packet queue limit to
<i>LEN</i> pkts</p>
<p style="margin-left:11%;"><b>-s,--script=SCRIPT</b></p>
<p style="margin-left:22%;">Invoke <i>SCRIPT</i> to
configure the network after connection. Without this,
routing and name service are unlikely to work correctly. The
script is expected to be compatible with the
<b>vpnc-script</b> which is shipped with the
"vpnc" VPN client. See
<i>http://www.infradead.org/openconnect/vpnc-script.html</i>
for more information. This version of OpenConnect is
configured to use <b>/etc/vpnc/vpnc-script</b> by
default.</p>
<p style="margin-left:22%; margin-top: 1em">On Windows, a
relative directory for the default script will be handled as
starting from the directory that the openconnect executable
is running from, rather than the current directory. The
script will be invoked with the command-based script host
<b>cscript.exe</b>.</p>
<p style="margin-left:11%;"><b>-S,--script-tun</b></p>
<p style="margin-left:22%;">Pass traffic to
’script’ program over a UNIX socket, instead of
to a kernel tun/tap device. This allows the VPN IP traffic
to be handled entirely in userspace, for example by a
program which uses lwIP to provide SOCKS access into the
VPN.</p>
<p style="margin-left:11%;"><b>-u,--user=NAME</b></p>
<p style="margin-left:22%;">Set login username to
<i>NAME</i></p>
<p style="margin-left:11%;"><b>-V,--version</b></p>
<p style="margin-left:22%;">Report version number</p>
<p style="margin-left:11%;"><b>-v,--verbose</b></p>
<p style="margin-left:22%;">More output (may be specified
multiple times for additional output)</p>
<p style="margin-left:11%;"><b>-x,--xmlconfig=CONFIG</b></p>
<p style="margin-left:22%;">XML config file</p>
<p style="margin-left:11%;"><b>--authgroup=GROUP</b></p>
<p style="margin-left:22%;">Choose authentication login
selection</p>
<p style="margin-left:11%;"><b>--authenticate</b></p>
<p style="margin-left:22%;">Authenticate only, and output
the information needed to make the connection a form which
can be used to set shell environment variables. When invoked
with this option, openconnect will not make the connection,
but if successful will output something like the following
to stdout: <b><br/>
COOKIE=3311180634@13561856@1339425499@B315A0E29D16C6FD92EE...
<br/>
HOST=10.0.0.1 <br/>
FINGERPRINT=469bb424ec8835944d30bc77c77e8fc1d8e23a42</b>
<br/>
Thus, you can invoke openconnect as a non-privileged user
<i>(with access to the user’s PKCS#11 tokens,
etc.)</i> for authentication, and then invoke openconnect
separately to make the actual connection as root: <b><br/>
eval ‘openconnect --authenticate
https://vpnserver.example.com‘; <br/>
[ -n $COOKIE ] && echo $COOKIE | <br/>
sudo openconnect --cookie-on-stdin $HOST --servercert
$FINGERPRINT</b></p>
<p style="margin-left:11%;"><b>--cookieonly</b></p>
<p style="margin-left:22%;">Fetch webvpn cookie only;
don’t connect</p>
<p style="margin-left:11%;"><b>--printcookie</b></p>
<p style="margin-left:22%;">Print webvpn cookie before
connecting</p>
<p style="margin-left:11%;"><b>--cafile=FILE</b></p>
<p style="margin-left:22%;">Cert file for server
verification</p>
<p style="margin-left:11%;"><b>--disable-ipv6</b></p>
<p style="margin-left:22%;">Do not advertise IPv6
capability to server</p>
<p style="margin-left:11%;"><b>--dtls-ciphers=LIST</b></p>
<p style="margin-left:22%;">Set OpenSSL ciphers to support
for DTLS</p>
<p style="margin-left:11%;"><b>--dtls-local-port=PORT</b></p>
<p style="margin-left:22%;">Use <i>PORT</i> as the local
port for DTLS datagrams</p>
<p style="margin-left:11%;"><b>--dump-http-traffic</b></p>
<p style="margin-left:22%;">Enable verbose output of all
HTTP requests and the bodies of all responses received from
the server.</p>
<p style="margin-left:11%;"><b>--no-system-trust</b></p>
<p style="margin-left:22%;">Do not trust the system default
certificate authorities. If this option is given, only
certificate authorities given with the
<b>--cafile</b> option, if any, will be trusted
automatically.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<colgroup><col width="11%"></col>
<col width="7%"></col>
<col width="4%" class="center"></col>
<col width="78%"></col>
</colgroup>
<tr valign="top" align="left">
<td></td>
<td>
<p><b>--pfs</b></p></td>
<td></td>
<td>
<p>Enforces Perfect Forward Secrecy (PFS). That ensures
that if the server’s long-term key is compromised, any
session keys established before the compromise will be
unaffected. If this option is provided and the server does
not support PFS in the TLS channel the connection will
fail.</p> </td></tr>
</table>
<p style="margin-left:22%; margin-top: 1em">PFS is
available in Cisco ASA releases 9.1(2) and higher; a
suitable cipher suite may need to be manually enabled by the
administrator using the <b>ssl encryption</b> setting.</p>
<p style="margin-left:11%;"><b>--no-dtls</b></p>
<p style="margin-left:22%;">Disable DTLS</p>
<p style="margin-left:11%;"><b>--no-http-keepalive</b></p>
<p style="margin-left:22%;">Version 8.2.2.5 of the Cisco
ASA software has a bug where it will forget the
client’s SSL certificate when HTTP connections are
being re-used for multiple requests. So far, this has
only been seen on the initial connection, where the server
gives an HTTP/1.0 redirect response with an explicit
<b>Connection: Keep-Alive</b> directive. OpenConnect
as of v2.22 has an unconditional workaround for this, which
is never to obey that directive after an HTTP/1.0
response.</p>
<p style="margin-left:22%; margin-top: 1em">However,
Cisco’s support team has failed to give any competent
response to the bug report and we don’t know under
what other circumstances their bug might manifest itself. So
this option exists to disable ALL re-use of HTTP
sessions and cause a new connection to be made for each
request. If your server seems not to be recognising your
certificate, try this option. If it makes a difference,
please report this information to the
<b>openconnect-devel@lists.infradead.org</b> mailing
list.</p>
<p style="margin-left:11%;"><b>--no-passwd</b></p>
<p style="margin-left:22%;">Never attempt password (or
SecurID) authentication.</p>
<p style="margin-left:11%;"><b>--no-xmlpost</b></p>
<p style="margin-left:22%;">Do not attempt to post an XML
authentication/configuration request to the server; use the
old style GET method which was used by older clients and
servers instead.</p>
<p style="margin-left:22%; margin-top: 1em">This option is
a temporary safety net, to work around potential
compatibility issues with the code which falls back to the
old method automatically. It causes OpenConnect to behave
more like older versions (4.08 and below) did. If you find
that you need to use this option, then you have found a bug
in OpenConnect. Please see
http://www.infradead.org/openconnect/mail.html and report
this to the developers.</p>
<p style="margin-left:11%;"><b>--non-inter</b></p>
<p style="margin-left:22%;">Do not expect user input; exit
if it is required.</p>
<p style="margin-left:11%;"><b>--passwd-on-stdin</b></p>
<p style="margin-left:22%;">Read password from standard
input</p>
<p style="margin-left:11%;"><b>--protocol=PROTO</b></p>
<p style="margin-left:22%;">Select VPN protocol
<i>PROTO</i> to be used for the connection. Supported
protocols are <i>anyconnect</i> for Cisco AnyConnect (the
default), and <i>nc</i> for experimental support for Juniper
Network Connect (also supported by Junos Pulse servers).</p>
<p style="margin-left:11%;"><b>--token-mode=MODE</b></p>
<p style="margin-left:22%;">Enable one-time password
generation using the <i>MODE</i> algorithm.
<b>--token-mode=rsa</b> will call
libstoken to generate an RSA SecurID tokencode,
<b>--token-mode=totp</b> will call liboath
to generate an RFC 6238 time-based password, and
<b>--token-mode=hotp</b> will call liboath
to generate an RFC 4226 HMAC-based password. Yubikey tokens
which generate OATH codes in hardware are supported with
<b>--token-mode=yubioath</b></p>
<p style="margin-left:11%;"><b>--token-secret={
SECRET[,COUNTER] | @FILENAME }</b></p>
<p style="margin-left:22%;">The secret to use when
generating one-time passwords/verification codes. Base
32-encoded TOTP/HOTP secrets can be used by specifying
"base32:" at the beginning of the secret, and for
HOTP secrets the token counter can be specified following a
comma.</p>
<p style="margin-left:22%; margin-top: 1em">RSA SecurID
secrets can be specified as an Android/iPhone URI or a raw
numeric CTF string (with or without dashes).</p>
<p style="margin-left:22%; margin-top: 1em">For Yubikey
OATH the token secret specifies the name of the credential
to be used. If not provided, the first OATH credential found
on the device will be used.</p>
<p style="margin-left:22%; margin-top: 1em"><i>FILENAME</i>,
if specified, can contain any of the above strings. Or, it
can contain a SecurID XML (SDTID) seed.</p>
<p style="margin-left:22%; margin-top: 1em">If this option
is omitted, and --token-mode is
"rsa", libstoken will try to use the software
token seed saved in <b>~/.stokenrc</b> by the "stoken
import" command.</p>
<p style="margin-left:11%;"><b>--reconnect-timeout</b></p>
<p style="margin-left:22%;">Keep reconnect attempts until
so much seconds are elapsed. The default timeout is 300
seconds, which means that openconnect can recover VPN
connection after a temporary network down time of 300
seconds.</p>
<p style="margin-left:11%;"><b>--resolve=HOST:IP</b></p>
<p style="margin-left:22%;">Automatically resolve the
hostname <i>HOST</i> to <i>IP</i> instead of using the
normal resolver to look it up.</p>
<p style="margin-left:11%;"><b>--servercert=HASH</b></p>
<p style="margin-left:22%;">Accept server’s SSL
certificate only if the provided fingerprint matches. The
allowed fingerprint types are <i>SHA1</i>, and
<i>SHA256</i>. They are distinguished by the
’sha1:’ or ’sha256:’ prefixes to the
hex encoded hash. To ease certain testing use-cases, a
partial match of the hash will also be accepted, if it is at
least 4 characters.</p>
<p style="margin-left:11%;"><b>--useragent=STRING</b></p>
<p style="margin-left:22%;">Use <i>STRING</i> as
’User-Agent:’ field value in HTTP header.
(e.g. --useragent ’Cisco AnyConnect VPN
Agent for Windows 2.2.0133’)</p>
<p style="margin-left:11%;"><b>--local-hostname=STRING</b></p>
<p style="margin-left:22%;">Use <i>STRING</i> as
’X-CSTP-Hostname:’ field value in
HTTP header. For example --local-hostname
’mypc’, will advertise the value
’mypc’ as the suggested hostname to point to the
provided IP address.</p>
<p style="margin-left:11%;"><b>--os=STRING</b></p>
<p style="margin-left:22%;">OS type to report to gateway.
Recognized values are: <b>linux</b>, <b>linux-64</b>,
<b>win</b>, <b>mac-intel</b>, <b>android</b>,
<b>apple-ios</b>. Reporting a different OS type may
affect the dynamic access policy (DAP) applied to the VPN
session. If the gateway requires CSD, it will also cause the
corresponding CSD trojan binary to be downloaded, so you may
need to use <b>--csd-wrapper</b> if this
code is not executable on the local machine.</p>
<h2 id="heading5">SIGNALS
</h2>
<p style="margin-left:11%; margin-top: 1em">In the data
phase of the connection, the following signals are
handled:</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<colgroup><col width="11%"></col>
<col width="9%"></col>
<col width="2%" class="center"></col>
<col width="78%"></col>
</colgroup>
<tr valign="top" align="left">
<td></td>
<td>
<p><b>SIGINT</b></p></td>
<td></td>
<td>
<p>performs a clean shutdown by logging the session off,
disconnecting from the gateway, and running the
vpnc-script to restore the network configuration.</p></td></tr>
<tr valign="top" align="left">
<td></td>
<td>
<p><b>SIGHUP</b></p></td>
<td></td>
<td>
<p>disconnects from the gateway and runs the
vpnc-script, but does not log the session off; this
allows for reconnection later using
<b>--cookie</b>.</p> </td></tr>
</table>
<p style="margin-left:11%;"><b>SIGUSR2</b></p>
<p style="margin-left:22%;">forces an immediate
disconnection and reconnection; this can be used to quickly
recover from LAN IP address changes.</p>
<p style="margin-left:11%;"><b>SIGTERM</b></p>
<p style="margin-left:22%;">exits immediately without
logging off or running vpnc-script.</p>
<h2 id="heading6">LIMITATIONS
</h2>
<p style="margin-left:11%; margin-top: 1em">Note that
although IPv6 has been tested on all platforms on which
<b>openconnect</b> is known to run, it depends on a suitable
<b>vpnc-script</b> to configure the network. The
standard <b>vpnc-script</b> shipped with vpnc 0.5.3 is
not capable of setting up IPv6 routes; the one from
<b>git://git.infradead.org/users/dwmw2/vpnc-scripts.git</b>
will be required.</p>
<h2 id="heading7">AUTHORS
</h2>
<p style="margin-left:11%; margin-top: 1em">David Woodhouse
<dwmw2@infradead.org></p>
<hr/>
</div>
</div>
</body>
</html>
distrib
>
Mageia
>
6
>
x86_64
>
media
>
core-updates
>
by-pkgid
>
089c2a9bd5c4c7d29319ed88551fed0e
>
files
>
34
