diff options
Diffstat (limited to 'man')
| -rw-r--r-- | man/Makefile.am | 4 | ||||
| -rw-r--r-- | man/Makefile.in | 110 | ||||
| -rw-r--r-- | man/ipsec.conf.5 | 778 | ||||
| -rw-r--r-- | man/ipsec.conf.5.in | 778 | ||||
| -rw-r--r-- | man/ipsec.secrets.5 | 54 | ||||
| -rw-r--r-- | man/ipsec.secrets.5.in | 52 | ||||
| -rw-r--r-- | man/strongswan.conf.5 | 524 | ||||
| -rw-r--r-- | man/strongswan.conf.5.in | 524 |
8 files changed, 1633 insertions, 1191 deletions
diff --git a/man/Makefile.am b/man/Makefile.am index a74a901b8..0becd24c7 100644 --- a/man/Makefile.am +++ b/man/Makefile.am @@ -5,7 +5,9 @@ CLEANFILES = ipsec.conf.5 ipsec.secrets.5 strongswan.conf.5 SUFFIXES = .in .in: + $(AM_V_GEN) \ sed \ -e "s:@IPSEC_VERSION@:$(PACKAGE_VERSION):" \ + -e "s:@DEV_URANDOM@:$(urandom_device):" \ + -e "s:@DEV_RANDOM@:$(random_device):" \ $(srcdir)/$@.in > $@ - diff --git a/man/Makefile.in b/man/Makefile.in index a38cf70ba..0bc64a6eb 100644 --- a/man/Makefile.in +++ b/man/Makefile.in @@ -1,9 +1,9 @@ -# Makefile.in generated by automake 1.11.1 from Makefile.am. +# Makefile.in generated by automake 1.11.6 from Makefile.am. # @configure_input@ # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, -# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, -# Inc. +# 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free Software +# Foundation, Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -15,6 +15,23 @@ @SET_MAKE@ VPATH = @srcdir@ +am__make_dryrun = \ + { \ + am__dry=no; \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + echo 'am--echo: ; @echo "AM" OK' | $(MAKE) -f - 2>/dev/null \ + | grep '^AM OK$$' >/dev/null || am__dry=yes;; \ + *) \ + for am__flg in $$MAKEFLAGS; do \ + case $$am__flg in \ + *=*|--*) ;; \ + *n*) am__dry=yes; break;; \ + esac; \ + done;; \ + esac; \ + test $$am__dry = yes; \ + } pkgdatadir = $(datadir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ @@ -45,14 +62,26 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/config/libtool.m4 \ $(top_srcdir)/m4/macros/with.m4 \ $(top_srcdir)/m4/macros/enable-disable.m4 \ $(top_srcdir)/m4/macros/add-plugin.m4 \ - $(top_srcdir)/configure.in + $(top_srcdir)/configure.ac am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ $(ACLOCAL_M4) mkinstalldirs = $(install_sh) -d +CONFIG_HEADER = $(top_builddir)/config.h CONFIG_CLEAN_FILES = CONFIG_CLEAN_VPATH_FILES = +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ SOURCES = DIST_SOURCES = +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; am__vpath_adj = case $$p in \ $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ @@ -74,6 +103,12 @@ am__nobase_list = $(am__nobase_strip_setup); \ am__base_list = \ sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' +am__uninstall_files_from_dir = { \ + test -z "$$files" \ + || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \ + || { echo " ( cd '$$dir' && rm -f" $$files ")"; \ + $(am__cd) "$$dir" && rm -f $$files; }; \ + } man5dir = $(mandir)/man5 am__installdirs = "$(DESTDIR)$(man5dir)" NROFF = nroff @@ -82,21 +117,28 @@ DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) ACLOCAL = @ACLOCAL@ ALLOCA = @ALLOCA@ AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ AR = @AR@ AUTOCONF = @AUTOCONF@ AUTOHEADER = @AUTOHEADER@ AUTOMAKE = @AUTOMAKE@ AWK = @AWK@ +BFDLIB = @BFDLIB@ BTLIB = @BTLIB@ CC = @CC@ CCDEPMODE = @CCDEPMODE@ CFLAGS = @CFLAGS@ +CHECK_CFLAGS = @CHECK_CFLAGS@ +CHECK_LIBS = @CHECK_LIBS@ +COVERAGE_CFLAGS = @COVERAGE_CFLAGS@ +COVERAGE_LDFLAGS = @COVERAGE_LDFLAGS@ CPP = @CPP@ CPPFLAGS = @CPPFLAGS@ CYGPATH_W = @CYGPATH_W@ DEFS = @DEFS@ DEPDIR = @DEPDIR@ DLLIB = @DLLIB@ +DLLTOOL = @DLLTOOL@ DSYMUTIL = @DSYMUTIL@ DUMPBIN = @DUMPBIN@ ECHO_C = @ECHO_C@ @@ -105,13 +147,16 @@ ECHO_T = @ECHO_T@ EGREP = @EGREP@ EXEEXT = @EXEEXT@ FGREP = @FGREP@ +GENHTML = @GENHTML@ GPERF = @GPERF@ +GPRBUILD = @GPRBUILD@ GREP = @GREP@ INSTALL = @INSTALL@ INSTALL_DATA = @INSTALL_DATA@ INSTALL_PROGRAM = @INSTALL_PROGRAM@ INSTALL_SCRIPT = @INSTALL_SCRIPT@ INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +LCOV = @LCOV@ LD = @LD@ LDFLAGS = @LDFLAGS@ LEX = @LEX@ @@ -124,6 +169,7 @@ LIPO = @LIPO@ LN_S = @LN_S@ LTLIBOBJS = @LTLIBOBJS@ MAKEINFO = @MAKEINFO@ +MANIFEST_TOOL = @MANIFEST_TOOL@ MKDIR_P = @MKDIR_P@ MYSQLCFLAG = @MYSQLCFLAG@ MYSQLCONFIG = @MYSQLCONFIG@ @@ -151,11 +197,13 @@ RANLIB = @RANLIB@ RTLIB = @RTLIB@ RUBY = @RUBY@ RUBYINCLUDE = @RUBYINCLUDE@ +RUBYLIB = @RUBYLIB@ SED = @SED@ SET_MAKE = @SET_MAKE@ SHELL = @SHELL@ SOCKLIB = @SOCKLIB@ STRIP = @STRIP@ +UNWINDLIB = @UNWINDLIB@ VERSION = @VERSION@ YACC = @YACC@ YFLAGS = @YFLAGS@ @@ -163,6 +211,7 @@ abs_builddir = @abs_builddir@ abs_srcdir = @abs_srcdir@ abs_top_builddir = @abs_top_builddir@ abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ ac_ct_CC = @ac_ct_CC@ ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ am__include = @am__include@ @@ -171,8 +220,6 @@ am__quote = @am__quote@ am__tar = @am__tar@ am__untar = @am__untar@ attest_plugins = @attest_plugins@ -axis2c_CFLAGS = @axis2c_CFLAGS@ -axis2c_LIBS = @axis2c_LIBS@ bindir = @bindir@ build = @build@ build_alias = @build_alias@ @@ -181,14 +228,19 @@ build_os = @build_os@ build_vendor = @build_vendor@ builddir = @builddir@ c_plugins = @c_plugins@ +charon_natt_port = @charon_natt_port@ +charon_plugins = @charon_plugins@ +charon_udp_port = @charon_udp_port@ clearsilver_LIBS = @clearsilver_LIBS@ +cmd_plugins = @cmd_plugins@ datadir = @datadir@ datarootdir = @datarootdir@ dbusservicedir = @dbusservicedir@ -default_pkcs11 = @default_pkcs11@ +dev_headers = @dev_headers@ docdir = @docdir@ dvidir = @dvidir@ exec_prefix = @exec_prefix@ +fips_mode = @fips_mode@ gtk_CFLAGS = @gtk_CFLAGS@ gtk_LIBS = @gtk_LIBS@ h_plugins = @h_plugins@ @@ -202,17 +254,17 @@ imcvdir = @imcvdir@ includedir = @includedir@ infodir = @infodir@ install_sh = @install_sh@ +ipsec_script = @ipsec_script@ +ipsec_script_upper = @ipsec_script_upper@ ipsecdir = @ipsecdir@ ipsecgroup = @ipsecgroup@ ipseclibdir = @ipseclibdir@ ipsecuser = @ipsecuser@ -libcharon_plugins = @libcharon_plugins@ libdir = @libdir@ libexecdir = @libexecdir@ linux_headers = @linux_headers@ localedir = @localedir@ localstatedir = @localstatedir@ -lt_ECHO = @lt_ECHO@ maemo_CFLAGS = @maemo_CFLAGS@ maemo_LIBS = @maemo_LIBS@ manager_plugins = @manager_plugins@ @@ -222,16 +274,15 @@ mkdir_p = @mkdir_p@ nm_CFLAGS = @nm_CFLAGS@ nm_LIBS = @nm_LIBS@ nm_ca_dir = @nm_ca_dir@ +nm_plugins = @nm_plugins@ oldincludedir = @oldincludedir@ openac_plugins = @openac_plugins@ -p_plugins = @p_plugins@ pcsclite_CFLAGS = @pcsclite_CFLAGS@ pcsclite_LIBS = @pcsclite_LIBS@ pdfdir = @pdfdir@ piddir = @piddir@ pki_plugins = @pki_plugins@ plugindir = @plugindir@ -pluto_plugins = @pluto_plugins@ pool_plugins = @pool_plugins@ prefix = @prefix@ program_transform_name = @program_transform_name@ @@ -305,11 +356,18 @@ clean-libtool: -rm -rf .libs _libs install-man5: $(dist_man_MANS) @$(NORMAL_INSTALL) - test -z "$(man5dir)" || $(MKDIR_P) "$(DESTDIR)$(man5dir)" - @list=''; test -n "$(man5dir)" || exit 0; \ - { for i in $$list; do echo "$$i"; done; \ - l2='$(dist_man_MANS)'; for i in $$l2; do echo "$$i"; done | \ - sed -n '/\.5[a-z]*$$/p'; \ + @list1=''; \ + list2='$(dist_man_MANS)'; \ + test -n "$(man5dir)" \ + && test -n "`echo $$list1$$list2`" \ + || exit 0; \ + echo " $(MKDIR_P) '$(DESTDIR)$(man5dir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(man5dir)" || exit 1; \ + { for i in $$list1; do echo "$$i"; done; \ + if test -n "$$list2"; then \ + for i in $$list2; do echo "$$i"; done \ + | sed -n '/\.5[a-z]*$$/p'; \ + fi; \ } | while read p; do \ if test -f $$p; then d=; else d="$(srcdir)/"; fi; \ echo "$$d$$p"; echo "$$p"; \ @@ -338,9 +396,7 @@ uninstall-man5: sed -n '/\.5[a-z]*$$/p'; \ } | sed -e 's,.*/,,;h;s,.*\.,,;s,^[^5][0-9a-z]*$$,5,;x' \ -e 's,\.[0-9a-z]*$$,,;$(transform);G;s,\n,.,'`; \ - test -z "$$files" || { \ - echo " ( cd '$(DESTDIR)$(man5dir)' && rm -f" $$files ")"; \ - cd "$(DESTDIR)$(man5dir)" && rm -f $$files; } + dir='$(DESTDIR)$(man5dir)'; $(am__uninstall_files_from_dir) tags: TAGS TAGS: @@ -408,10 +464,15 @@ install-am: all-am installcheck: installcheck-am install-strip: - $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ - install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ - `test -z '$(STRIP)' || \ - echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi mostlyclean-generic: clean-generic: @@ -508,8 +569,11 @@ uninstall-man: uninstall-man5 .in: + $(AM_V_GEN) \ sed \ -e "s:@IPSEC_VERSION@:$(PACKAGE_VERSION):" \ + -e "s:@DEV_URANDOM@:$(urandom_device):" \ + -e "s:@DEV_RANDOM@:$(random_device):" \ $(srcdir)/$@.in > $@ # Tell versions [3.59,3.63) of GNU make to not export all variables. diff --git a/man/ipsec.conf.5 b/man/ipsec.conf.5 index 0a7f8bfe5..76bef614f 100644 --- a/man/ipsec.conf.5 +++ b/man/ipsec.conf.5 @@ -1,4 +1,4 @@ -.TH IPSEC.CONF 5 "2011-12-14" "4.6.4" "strongSwan" +.TH IPSEC.CONF 5 "2012-06-26" "5.1.0" "strongSwan" .SH NAME ipsec.conf \- IPsec configuration and connections .SH DESCRIPTION @@ -172,9 +172,9 @@ keying, rekeying, and general control. The path to control the connection is called 'ISAKMP SA' in IKEv1 and 'IKE SA' in the IKEv2 protocol. That what is being negotiated, the kernel level data path, is called 'IPsec SA' or 'Child SA'. -strongSwan currently uses two separate keying daemons. \fIpluto\fP handles -all IKEv1 connections, \fIcharon\fP is the daemon handling the IKEv2 -protocol. +strongSwan previously used two separate keying daemons, \fIpluto\fP and +\fIcharon\fP. This manual does not discuss \fIpluto\fP options anymore, but +only \fIcharon\fP that since strongSwan 5.0 supports both IKEv1 and IKEv2. .PP To avoid trivial editing of the configuration file to suit it to each system involved in a connection, @@ -233,21 +233,14 @@ defines the identity of the AAA backend used during IKEv2 EAP authentication. This is required if the EAP client uses a method that verifies the server identity (such as EAP-TLS), but it does not match the IKEv2 gateway identity. .TP +.BR aggressive " = yes | " no +whether to use IKEv1 Aggressive or Main Mode (the default). +.TP .BR also " = <name>" includes conn section .BR <name> . .TP -.BR auth " = " esp " | ah" -whether authentication should be done as part of -ESP encryption, or separately using the AH protocol; -acceptable values are -.B esp -(the default) and -.BR ah . -.br -The IKEv2 daemon currently supports ESP only. -.TP -.BR authby " = " pubkey " | rsasig | ecdsasig | psk | eap | never | xauth..." +.BR authby " = " pubkey " | rsasig | ecdsasig | psk | secret | never | xauthpsk | xauthrsasig" how the two security gateways should authenticate each other; acceptable values are .B psk @@ -268,17 +261,12 @@ IKEv1 additionally supports the values .B xauthpsk and .B xauthrsasig -that will enable eXtended Authentication (XAuth) in addition to IKEv1 main mode -based on shared secrets or digital RSA signatures, respectively. -IKEv2 additionally supports the value -.BR eap , -which indicates an initiator to request EAP authentication. The EAP method -to use is selected by the server (see -.BR eap ). -This parameter is deprecated for IKEv2 connections, as two peers do not need -to agree on an authentication method. Use the +that will enable eXtended AUTHentication (XAUTH) in addition to IKEv1 main mode +based on shared secrets or digital RSA signatures, respectively. +This parameter is deprecated, as two peers do not need to agree on an +authentication method in IKEv2. Use the .B leftauth -parameter instead to define authentication methods in IKEv2. +parameter instead to define authentication methods. .TP .BR auto " = " ignore " | add | route | start" what operation, if any, should be done automatically at IPsec startup; @@ -295,18 +283,24 @@ loads a connection without starting it. loads a connection and installs kernel traps. If traffic is detected between .B leftsubnet and -.B rightsubnet -, a connection is established. +.BR rightsubnet , +a connection is established. .B start loads a connection and brings it up immediately. .B ignore -ignores the connection. This is equal to delete a connection from the config +ignores the connection. This is equal to deleting a connection from the config file. -Relevant only locally, other end need not agree on it -(but in general, for an intended-to-be-permanent connection, -both ends should use -.B auto=start -to ensure that any reboot causes immediate renegotiation). +Relevant only locally, other end need not agree on it. +.TP +.BR closeaction " = " none " | clear | hold | restart" +defines the action to take if the remote peer unexpectedly closes a CHILD_SA +(see +.B dpdaction +for meaning of values). +A +.B closeaction should not be +used if the peer uses reauthentication or uniquids checking, as these events +might trigger the defined action when not desired. .TP .BR compress " = yes | " no whether IPComp compression of content is proposed on the connection @@ -318,12 +312,11 @@ and .B no (the default). A value of .B yes -causes IPsec to propose both compressed and uncompressed, +causes the daemon to propose both compressed and uncompressed, and prefer compressed. A value of .B no -prevents IPsec from proposing compression; -a proposal to compress will still be accepted. +prevents the daemon from proposing or accepting compression. .TP .BR dpdaction " = " none " | clear | hold | restart" controls the use of the Dead Peer Detection protocol (DPD, RFC 3706) where @@ -341,16 +334,9 @@ put in the hold state .RB ( hold ) or restarted .RB ( restart ). -For IKEv1, the default is -.B none -which disables the active sending of R_U_THERE notifications. -Nevertheless pluto will always send the DPD Vendor ID during connection set up -in order to signal the readiness to act passively as a responder if the peer -wants to use DPD. For IKEv2, +The default is .B none -does't make sense, since all messages are used to detect dead peers. If specified, -it has the same meaning as the default -.RB ( clear ). +which disables the active sending of DPD messages. .TP .BR dpddelay " = " 30s " | <time>" defines the period time interval with which R_U_THERE messages/INFORMATIONAL @@ -359,58 +345,17 @@ received. In IKEv2, a value of 0 sends no additional INFORMATIONAL messages and uses only standard messages (such as those to rekey) to detect dead peers. .TP -.BR dpdtimeout " = " 150s " | <time>" +.BR dpdtimeout " = " 150s " | <time> defines the timeout interval, after which all connections to a peer are deleted in case of inactivity. This only applies to IKEv1, in IKEv2 the default retransmission timeout applies, as every exchange is used to detect dead peers. -See -.IR strongswan.conf (5) -for a description of the IKEv2 retransmission timeout. -.TP -.BR closeaction " = " none " | clear | hold | restart" -defines the action to take if the remote peer unexpectedly closes a CHILD_SA -(IKEv2 only, see dpdaction for meaning of values). A closeaction should not be -used if the peer uses reauthentication or uniquids checking, as these events -might trigger a closeaction when not desired. .TP .BR inactivity " = <time>" defines the timeout interval, after which a CHILD_SA is closed if it did -not send or receive any traffic. Currently supported in IKEv2 connections only. -.TP -.BR eap " = aka | ... | radius | ... | <type> | <type>-<vendor> -defines the EAP type to propose as server if the client requests EAP -authentication. Currently supported values are -.B aka -for EAP-AKA, -.B gtc -for EAP-GTC, -.B md5 -for EAP-MD5, -.B mschapv2 -for EAP-MS-CHAPv2, -.B peap -for EAP-PEAPv0, -.B radius -for the EAP-RADIUS proxy, -.B sim -for EAP-SIM, -.B tls -for EAP-TLS, and -.B ttls -for EAP-TTLSv0. -Additionally, IANA assigned EAP method numbers are accepted, or a -definition in the form -.B eap=type-vendor -(e.g. eap=7-12345) can be used to specify vendor specific EAP types. -This parameter is deprecated in the favour of -.B leftauth. - -To forward EAP authentication to a RADIUS server using the EAP-RADIUS plugin, -set -.BR eap=radius . +not send or receive any traffic. .TP .BR eap_identity " = <id>" -defines the identity the client uses to reply to a EAP Identity request. +defines the identity the client uses to reply to an EAP Identity request. If defined on the EAP server, the defined identity will be used as peer identity during EAP authentication. The special value .B %identity @@ -423,17 +368,17 @@ for the connection, e.g. .BR aes128-sha256 . The notation is .BR encryption-integrity[-dhgroup][-esnmode] . -.br + Defaults to -.BR aes128-sha1,3des-sha1 -for IKEv1. The IKEv2 daemon adds its extensive default proposal to this default +.BR aes128-sha1,3des-sha1 . +The daemon adds its extensive default proposal to this default or the configured value. To restrict it to the configured proposal an exclamation mark .RB ( ! ) can be added at the end. -.br + .BR Note : -As a responder both daemons accept the first supported proposal received from +As a responder the daemon accepts the first supported proposal received from the peer. In order to restrict a responder to only accept specific cipher suites, the strict flag .RB ( ! , @@ -441,8 +386,8 @@ exclamation mark) can be used, e.g: aes256-sha512-modp4096! .br If .B dh-group -is specified, CHILD_SA setup and rekeying include a separate Diffie-Hellman -exchange (IKEv2 only). Valid values for +is specified, CHILD_SA/Quick Mode setup and rekeying include a separate +Diffie-Hellman exchange. Valid values for .B esnmode (IKEv2 only) are .B esn @@ -455,39 +400,69 @@ the default is .BR forceencaps " = yes | " no force UDP encapsulation for ESP packets even if no NAT situation is detected. This may help to surmount restrictive firewalls. In order to force the peer to -encapsulate packets, NAT detection payloads are faked (IKEv2 only). +encapsulate packets, NAT detection payloads are faked. +.TP +.BR fragmentation " = yes | force | " no +whether to use IKE fragmentation (proprietary IKEv1 extension). Acceptable +values are +.BR yes , +.B force +and +.B no +(the default). Fragmented messages sent by a peer are always accepted +irrespective of the value of this option. If set to +.BR yes , +and the peer supports it, larger IKE messages will be sent in fragments. +If set to +.B force +the initial IKE message will already be fragmented if required. .TP .BR ike " = <cipher suites>" comma-separated list of IKE/ISAKMP SA encryption/authentication algorithms to be used, e.g. .BR aes128-sha1-modp2048 . The notation is -.BR encryption-integrity-dhgroup . -In IKEv2, multiple algorithms and proposals may be included, such as -aes128-aes256-sha1-modp1536-modp2048,3des-sha1-md5-modp1024. +.BR encryption-integrity[-prf]-dhgroup . +If no PRF is given, the algorithms defined for integrity are used for the PRF. +The prf keywords are the same as the integrity algorithms, but have a +.B prf +prefix (such as +.BR prfsha1 , +.B prfsha256 +or +.BR prfaesxcbc ). .br +In IKEv2, multiple algorithms and proposals may be included, such as +.BR aes128-aes256-sha1-modp1536-modp2048,3des-sha1-md5-modp1024 . + Defaults to -.B aes128-sha1-modp2048,3des-sha1-modp1536 -for IKEv1. The IKEv2 daemon adds its extensive default proposal to this +.BR aes128-sha1-modp2048,3des-sha1-modp1536 . +The daemon adds its extensive default proposal to this default or the configured value. To restrict it to the configured proposal an exclamation mark .RB ( ! ) can be added at the end. -.br + .BR Note : -As a responder both daemons accept the first supported proposal received from +As a responder the daemon accepts the first supported proposal received from the peer. In order to restrict a responder to only accept specific cipher suites, the strict flag -.BR ( ! , -exclamation mark) can be used, e.g: aes256-sha512-modp4096! +.RB ( ! , +exclamation mark) can be used, e.g: +.BR aes256-sha512-modp4096! +.TP +.BR ikedscp " = " 000000 " | <DSCP field>" +Differentiated Services Field Codepoint to set on outgoing IKE packets sent +from this connection. The value is a six digit binary encoded string defining +the Codepoint to set, as defined in RFC 2474. .TP .BR ikelifetime " = " 3h " | <time>" how long the keying channel of a connection (ISAKMP or IKE SA) should last before being renegotiated. Also see EXPIRY/REKEY below. .TP .BR installpolicy " = " yes " | no" -decides whether IPsec policies are installed in the kernel by the IKEv2 -charon daemon for a given connection. Allows peaceful cooperation e.g. with +decides whether IPsec policies are installed in the kernel by the charon daemon +for a given connection. Allows peaceful cooperation e.g. with the Mobile IPv6 daemon mip6d who wants to control the kernel policies. Acceptable values are .B yes @@ -495,21 +470,10 @@ Acceptable values are .BR no . .TP .BR keyexchange " = " ike " | ikev1 | ikev2" -method of key exchange; -which protocol should be used to initialize the connection. Connections marked with -.B ikev1 -are initiated with pluto, those marked with -.B ikev2 -with charon. An incoming request from the remote peer is handled by the correct -daemon, unaffected from the -.B keyexchange -setting. Starting with strongSwan 4.5 the default value +which key exchange protocol should be used to initiate the connection. +Connections marked with .B ike -is a synonym for -.BR ikev2 , -whereas in older strongSwan releases -.B ikev1 -was assumed. +use IKEv2 when initiating, but accept any protocol version when responding. .TP .BR keyingtries " = " 3 " | <number> | %forever" how many attempts (a whole number or \fB%forever\fP) should be made to @@ -524,45 +488,23 @@ Relevant only locally, other end need not agree on it. synonym for .BR lifetime . .TP -.BR left " = <ip address> | <fqdn> | %defaultroute | " %any +.BR left " = <ip address> | <fqdn> | " %any (required) the IP address of the left participant's public-network interface or one of several magic values. -If it is -.BR %defaultroute , -.B left -will be filled in automatically with the local address -of the default-route interface (as determined at IPsec startup time and -during configuration update). -Either -.B left -or -.B right -may be -.BR %defaultroute , -but not both. -The prefix -.B % -in front of a fully-qualified domain name or an IP address will implicitly set -.B leftallowany=yes. -If the domain name cannot be resolved into an IP address at IPsec startup or -update time then -.B left=%any -and -.B leftallowany=no -will be assumed. - -In case of an IKEv2 connection, the value +The value .B %any -for the local endpoint signifies an address to be filled in (by automatic -keying) during negotiation. If the local peer initiates the connection setup -the routing table will be queried to determine the correct local IP address. +(the default) for the local endpoint signifies an address to be filled in (by +automatic keying) during negotiation. If the local peer initiates the +connection setup the routing table will be queried to determine the correct +local IP address. In case the local peer is responding to a connection setup then any IP address that is assigned to a local interface will be accepted. -.br -Note that specifying -.B %any -for the local endpoint is not supported by the IKEv1 pluto daemon. + +The prefix +.B % +in front of a fully-qualified domain name or an IP address will implicitly set +.BR leftallowany =yes. If .B %any @@ -574,35 +516,37 @@ is used in that case. .TP .BR leftallowany " = yes | " no a modifier for -.B left -, making it behave as +.BR left , +making it behave as .B %any -although a concrete IP address has been assigned. -Recommended for dynamic IP addresses that can be resolved by DynDNS at IPsec -startup or update time. -Acceptable values are -.B yes -and -.B no -(the default). +although a concrete IP address or domain name has been assigned. .TP .BR leftauth " = <auth method>" Authentication method to use locally (left) or require from the remote (right) side. -This parameter is supported in IKEv2 only. Acceptable values are +Acceptable values are .B pubkey for public key authentication (RSA/ECDSA), .B psk -for pre-shared key authentication and +for pre-shared key authentication, .B eap -to (require the) use of the Extensible Authentication Protocol. +to (require the) use of the Extensible Authentication Protocol in IKEv2, and +.B xauth +for IKEv1 eXtended Authentication. To require a trustchain public key strength for the remote side, specify the -key type followed by the strength in bits (for example -.BR rsa-2048 +key type followed by the minimum strength in bits (for example +.BR ecdsa-384 +or +.BR rsa-2048-ecdsa-256 ). +To limit the acceptable set of hashing algorithms for trustchain validation, +append hash algorithms to +.BR pubkey +or a key strength definition (for example +.BR pubkey-sha1-sha256 or -.BR ecdsa-256 ). +.BR rsa-2048-ecdsa-256-sha256-sha384-sha512 ). For -.B eap, +.BR eap , an optional EAP method can be appended. Currently defined methods are .BR eap-aka , .BR eap-gtc , @@ -611,25 +555,41 @@ an optional EAP method can be appended. Currently defined methods are .BR eap-peap , .BR eap-sim , .BR eap-tls , +.BR eap-ttls , +.BR eap-dynamic , and -.BR eap-ttls . +.BR eap-radius . Alternatively, IANA assigned EAP method numbers are accepted. Vendor specific EAP methods are defined in the form .B eap-type-vendor .RB "(e.g. " eap-7-12345 ). +For +.B xauth, +an XAuth authentication backend can be specified, such as +.B xauth-generic +or +.BR xauth-eap . +If XAuth is used in +.BR leftauth , +Hybrid authentication is used. For traditional XAuth authentication, define +XAuth in +.BR lefauth2 . .TP .BR leftauth2 " = <auth method>" Same as .BR leftauth , -but defines an additional authentication exchange. IKEv2 supports multiple +but defines an additional authentication exchange. In IKEv1, only XAuth can be +used in the second authentication round. IKEv2 supports multiple complete authentication rounds using "Multiple Authentication Exchanges" defined -in RFC4739. This allows, for example, separated authentication -of host and user (IKEv2 only). +in RFC 4739. This allows, for example, separated authentication +of host and user. .TP .BR leftca " = <issuer dn> | %same" the distinguished name of a certificate authority which is required to lie in the trust path going from the left participant's certificate up to the root certification authority. +.B %same +means that the value configured for the right participant should be reused. .TP .BR leftca2 " = <issuer dn> | %same" Same as @@ -644,12 +604,23 @@ are accepted. By default .B leftcert sets .B leftid -to the distinguished name of the certificate's subject and -.B leftca -to the distinguished name of the certificate's issuer. +to the distinguished name of the certificate's subject. The left participant's ID can be overridden by specifying a .B leftid value which must be certified by the certificate, though. +.br +A value in the form +.B %smartcard[<slot nr>[@<module>]]:<keyid> +defines a specific certificate to load from a PKCS#11 backend for this +connection. See ipsec.secrets(5) for details about smartcard definitions. +.B leftcert +is required only if selecting the certificate with +.B leftid +is not sufficient, for example if multiple certificates use the same subject. +.br +Multiple certificate paths or PKCS#11 backends can be specified in a comma +separated list. The daemon chooses the certificate based on the received +certificate requests if possible before enforcing the first. .TP .BR leftcert2 " = <path>" Same as @@ -657,8 +628,17 @@ Same as but for the second authentication round (IKEv2 only). .TP .BR leftcertpolicy " = <OIDs>" -Comma separated list of certificate policy OIDs the peers certificate must have. -OIDs are specified using the numerical dotted representation (IKEv2 only). +Comma separated list of certificate policy OIDs the peer's certificate must +have. +OIDs are specified using the numerical dotted representation. +.TP +.BR leftdns " = <servers>" +Comma separated list of DNS server addresses to exchange as configuration +attributes. On the initiator, a server is a fixed IPv4/IPv6 address, or +.BR %config4 / %config6 +to request attributes without an address. On the responder, +only fixed IPv4/IPv6 addresses are allowed and define DNS servers assigned +to the client. .TP .BR leftfirewall " = yes | " no whether the left participant is doing forwarding-firewalling @@ -683,8 +663,7 @@ tunnels established with IPsec are exempted from it so that packets can flow unchanged through the tunnels. (This means that all subnets connected in this manner must have distinct, non-overlapping subnet address blocks.) -This is done by the default \fBipsec _updown\fR script (see -.IR pluto (8)). +This is done by the default \fBipsec _updown\fR script. In situations calling for more control, it may be preferable for the user to supply his own @@ -696,12 +675,13 @@ which makes the appropriate adjustments for his system. a comma separated list of group names. If the .B leftgroups parameter is present then the peer must be a member of at least one -of the groups defined by the parameter. Group membership must be certified -by a valid attribute certificate stored in \fI/etc/ipsec.d/acerts/\fP thas has -been issued to the peer by a trusted Authorization Authority stored in -\fI/etc/ipsec.d/aacerts/\fP. -.br -Attribute certificates are not supported in IKEv2 yet. +of the groups defined by the parameter. +.TP +.BR leftgroups2 " = <group list>" +Same as +.B leftgroups, +but for the second authentication round defined with +.B leftauth2. .TP .BR lefthostaccess " = yes | " no inserts a pair of INPUT and OUTPUT iptables rules using the default @@ -717,10 +697,25 @@ and .BR leftid " = <id>" how the left participant should be identified for authentication; defaults to -.BR left . -Can be an IP address or a fully-qualified domain name preceded by -.B @ -(which is used as a literal string and not resolved). +.B left +or the subject of the certificate configured with +.BR leftcert . +Can be an IP address, a fully-qualified domain name, an email address, or +a keyid. If +.B leftcert +is configured the identity has to be confirmed by the certificate. + +For IKEv2 and +.B rightid +the prefix +.B % +in front of the identity prevents the daemon from sending IDr in its IKE_AUTH +request and will allow it to verify the configured identity against the subject +and subjectAltNames contained in the responder's certificate (otherwise it is +only compared with the IDr returned by the responder). The IDr sent by the +initiator might otherwise prevent the responder from finding a config if it +has configured a different value for +.BR leftid . .TP .BR leftid2 " = <id>" identity to use for a second authentication for the left participant @@ -728,51 +723,30 @@ identity to use for a second authentication for the left participant .BR leftid . .TP .BR leftikeport " = <port>" -UDP port the left participant uses for IKE communication. Currently supported in -IKEv2 connections only. If unspecified, port 500 is used with the port floating +UDP port the left participant uses for IKE communication. +If unspecified, port 500 is used with the port floating to 4500 if a NAT is detected or MOBIKE is enabled. Specifying a local IKE port different from the default additionally requires a socket implementation that -listens to this port. -.TP -.BR leftnexthop " = %direct | %defaultroute | <ip address> | <fqdn>" -this parameter is usually not needed any more because the NETKEY IPsec stack -does not require explicit routing entries for the traffic to be tunneled. If -.B leftsourceip -is used with IKEv1 then -.B leftnexthop -must still be set in order for the source routes to work properly. +listens on this port. .TP .BR leftprotoport " = <protocol>/<port>" -restrict the traffic selector to a single protocol and/or port. -Examples: -.B leftprotoport=tcp/http +restrict the traffic selector to a single protocol and/or port. This option +is now deprecated, protocol/port information can be defined for each subnet +directly in +.BR leftsubnet . +.TP +.BR leftsigkey " = <raw public key> | <path to public key>" +the left participant's public key for public key signature authentication, +in PKCS#1 format using hex (0x prefix) or base64 (0s prefix) encoding. With the +optional +.B dns: or -.B leftprotoport=6/80 -or -.B leftprotoport=udp -.TP -.BR leftrsasigkey " = " %cert " | <raw rsa public key>" -the left participant's -public key for RSA signature authentication, -in RFC 2537 format using -.IR ttodata (3) +.B ssh: +prefix in front of 0x or 0s, the public key is expected to be in either +the RFC 3110 (not the full RR, only RSA key part) or RFC 4253 public key format, +respectively. +Also accepted is the path to a file containing the public key in PEM or DER encoding. -The magic value -.B %none -means the same as not specifying a value (useful to override a default). -The value -.B %cert -(the default) -means that the key is extracted from a certificate. -The identity used for the left participant -must be a specific host, not -.B %any -or another magic value. -.B Caution: -if two connection descriptions -specify different public keys for the same -.BR leftid , -confusion and madness will ensue. .TP .BR leftsendcert " = never | no | " ifasked " | always | yes" Accepted values are @@ -787,20 +761,25 @@ and the latter meaning that the peer must send a certificate request payload in order to get a certificate in return. .TP -.BR leftsourceip " = %config | %cfg | %modeconfig | %modecfg | <ip address>" -The internal source IP to use in a tunnel, also known as virtual IP. If the -value is one of the synonyms +.BR leftsourceip " = %config4 | %config6 | <ip address>" +Comma separated list of internal source IPs to use in a tunnel, also known as +virtual IP. If the value is one of the synonyms .BR %config , .BR %cfg , .BR %modeconfig , or .BR %modecfg , -an address is requested from the peer. In IKEv2, a statically defined address -is also requested, since the server may change it. +an address (from the tunnel address family) is requested from the peer. With +.B %config4 +and +.B %config6 +an address of the given address family will be requested explicitly. +If an IP address is configured, it will be requested from the responder, +which is free to respond with a different address. .TP .BR rightsourceip " = %config | <network>/<netmask> | %poolname" -The internal source IP to use in a tunnel for the remote peer. If the -value is +Comma separated list of internal source IPs to use in a tunnel for the remote +peer. If the value is .B %config on the responder side, the initiator must propose an address which is then echoed back. Also supported are address pools expressed as @@ -808,21 +787,47 @@ echoed back. Also supported are address pools expressed as or the use of an external IP address pool using %\fIpoolname\fR, where \fIpoolname\fR is the name of the IP address pool used for the lookup. .TP -.BR leftsubnet " = <ip subnet>" +.BR leftsubnet " = <ip subnet>[[<proto/port>]][,...]" private subnet behind the left participant, expressed as \fInetwork\fB/\fInetmask\fR; if omitted, essentially assumed to be \fIleft\fB/32\fR, signifying that the left end of the connection goes to the left participant -only. When using IKEv2, the configured subnet of the peers may differ, the -protocol narrows it to the greatest common subnet. Further, IKEv2 supports -multiple subnets separated by commas. IKEv1 only interprets the first subnet -of such a definition. -.TP -.BR leftsubnetwithin " = <ip subnet>" -the peer can propose any subnet or single IP address that fits within the -range defined by -.BR leftsubnetwithin. -Not relevant for IKEv2, as subnets are narrowed. +only. Configured subnets of the peers may differ, the protocol narrows it to +the greatest common subnet. In IKEv1, this may lead to problems with other +implementations, make sure to configure identical subnets in such +configurations. IKEv2 supports multiple subnets separated by commas. IKEv1 only +interprets the first subnet of such a definition, unless the Cisco Unity +extension plugin is enabled. + +The optional part after each subnet enclosed in square brackets specifies a +protocol/port to restrict the selector for that subnet. + +Examples: +.BR leftsubnet=10.0.0.1[tcp/http],10.0.0.2[6/80] " or" +.BR leftsubnet=fec1::1[udp],10.0.0.0/16[/53] . +Instead of omitting either value +.B %any +can be used to the same effect, e.g. +.BR leftsubnet=fec1::1[udp/%any],10.0.0.0/16[%any/53] . + +The port value can alternatively take the value +.B %opaque +for RFC 4301 OPAQUE selectors, or a numerical range in the form +.BR 1024-65535 . +None of the kernel backends currently supports opaque or port ranges and uses +.B %any +for policy installation instead. + +Instead of specifying a subnet, +.B %dynamic +can be used to replace it with the IKE address, having the same effect +as omitting +.B leftsubnet +completely. Using +.B %dynamic +can be used to define multiple dynamic selectors, each having a potentially +different protocol/port definition. + .TP .BR leftupdown " = <path>" what ``updown'' script to run to adjust routing and/or firewalling @@ -832,20 +837,15 @@ changes (default May include positional parameters separated by white space (although this requires enclosing the whole string in quotes); including shell metacharacters is unwise. -See -.IR pluto (8) -for details. -Relevant only locally, other end need not agree on it. IKEv2 uses the updown +Relevant only locally, other end need not agree on it. Charon uses the updown script to insert firewall rules only, since routing has been implemented -directly into charon. +directly into the daemon. .TP .BR lifebytes " = <number>" -the number of bytes transmitted over an IPsec SA before it expires (IKEv2 -only). +the number of bytes transmitted over an IPsec SA before it expires. .TP .BR lifepackets " = <number>" -the number of packets transmitted over an IPsec SA before it expires (IKEv2 -only). +the number of packets transmitted over an IPsec SA before it expires. .TP .BR lifetime " = " 1h " | <time>" how long a particular instance of a connection @@ -877,12 +877,12 @@ which thinks the lifetime is longer. Also see EXPIRY/REKEY below. .BR marginbytes " = <number>" how many bytes before IPsec SA expiry (see .BR lifebytes ) -should attempts to negotiate a replacement begin (IKEv2 only). +should attempts to negotiate a replacement begin. .TP .BR marginpackets " = <number>" how many packets before IPsec SA expiry (see .BR lifepackets ) -should attempts to negotiate a replacement begin (IKEv2 only). +should attempts to negotiate a replacement begin. .TP .BR margintime " = " 9m " | <time>" how long before connection expiry or keying-channel expiry @@ -921,7 +921,7 @@ enables the IKEv2 MOBIKE protocol defined by RFC 4555. Accepted values are .BR no . If set to .BR no , -the IKEv2 charon daemon will not actively propose MOBIKE as initiator and +the charon daemon will not actively propose MOBIKE as initiator and ignore the MOBIKE_SUPPORTED notify as responder. .TP .BR modeconfig " = push | " pull @@ -931,29 +931,8 @@ Accepted values are and .B pull (the default). -Currently relevant for IKEv1 only since IKEv2 always uses the configuration -payload in pull mode. Cisco VPN gateways usually operate in -.B push -mode. -.TP -.BR pfs " = " yes " | no" -whether Perfect Forward Secrecy of keys is desired on the connection's -keying channel -(with PFS, penetration of the key-exchange protocol -does not compromise keys negotiated earlier); -acceptable values are -.B yes -(the default) -and -.BR no. -IKEv2 always uses PFS for IKE_SA rekeying whereas for CHILD_SA rekeying -PFS is enforced by defining a Diffie-Hellman modp group in the -.B esp -parameter. -.TP -.BR pfsgroup " = <modp group>" -defines a Diffie-Hellman group for perfect forward secrecy in IKEv1 Quick Mode -differing from the DH group used for IKEv1 Main Mode (IKEv1 only). +Push mode is currently not supported in charon, hence this parameter has no +effect. .TP .BR reauth " = " yes " | no" whether rekeying of an IKE_SA should also reauthenticate the peer. In IKEv1, @@ -973,11 +952,12 @@ and .BR no . The two ends need not agree, but while a value of .B no -prevents pluto/charon from requesting renegotiation, +prevents charon from requesting renegotiation, it does not prevent responding to renegotiation requested from the other end, so .B no -will be largely ineffective unless both ends agree on it. +will be largely ineffective unless both ends agree on it. Also see +.BR reauth . .TP .BR rekeyfuzz " = " 100% " | <percentage>" maximum percentage by which @@ -1035,11 +1015,7 @@ signifying the special Mobile IPv6 transport proxy mode; .BR passthrough , signifying that no IPsec processing should be done at all; .BR drop , -signifying that packets should be discarded; and -.BR reject , -signifying that packets should be discarded and a diagnostic ICMP returned -.RB ( reject -is currently not supported by the NETKEY stack of the Linux 2.6 kernel). +signifying that packets should be discarded. .TP .BR xauth " = " client " | server" specifies the role in the XAuth protocol if activated by @@ -1105,6 +1081,11 @@ currently can have either the value .BR cacert " = <path>" defines a path to the CA certificate either relative to \fI/etc/ipsec.d/cacerts\fP or as an absolute path. +.br +A value in the form +.B %smartcard[<slot nr>[@<module>]]:<keyid> +defines a specific CA certificate to load from a PKCS#11 backend for this CA. +See ipsec.secrets(5) for details about smartcard definitions. .TP .BR crluri " = <uri>" defines a CRL distribution point (ldap, http, or file URI) @@ -1116,8 +1097,6 @@ synonym for .BR crluri2 " = <uri>" defines an alternative CRL distribution point (ldap, http, or file URI) .TP -.BR ldaphost " = <hostname>" -defines an ldap host. Currently used by IKEv1 only. .TP .BR ocspuri " = <uri>" defines an OCSP URI. @@ -1127,11 +1106,11 @@ synonym for .B ocspuri. .TP .BR ocspuri2 " = <uri>" -defines an alternative OCSP URI. Currently used by IKEv2 only. +defines an alternative OCSP URI. .TP .BR certuribase " = <uri>" defines the base URI for the Hash and URL feature supported by IKEv2. -Instead of exchanging complete certificates, IKEv2 allows to send an URI +Instead of exchanging complete certificates, IKEv2 allows one to send an URI that resolves to the DER encoded certificate. The certificate URIs are built by appending the SHA1 hash of the DER encoded certificates to this base URI. .SH "CONFIG SECTIONS" @@ -1140,48 +1119,34 @@ At present, the only section known to the IPsec software is the one named .BR setup , which contains information used when the software is being started. -Here's an example: -.PP -.ne 8 -.nf -.ft B -.ta 1c -config setup - plutodebug=all - crlcheckinterval=10m - strictcrlpolicy=yes -.ft -.fi -.PP -Parameters are optional unless marked ``(required)''. The currently-accepted .I parameter names in a .B config .B setup -section affecting both daemons are: +section are: .TP .BR cachecrls " = yes | " no -certificate revocation lists (CRLs) fetched via http or ldap will be cached in -\fI/etc/ipsec.d/crls/\fR under a unique file name derived from the certification -authority's public key. -Accepted values are -.B yes -and -.B no -(the default). Only relevant for IKEv1, as CRLs are always cached in IKEv2. +if enabled, certificate revocation lists (CRLs) fetched via HTTP or LDAP will +be cached in +.I /etc/ipsec.d/crls/ +under a unique file name derived from the certification authority's public key. .TP -.BR charonstart " = " yes " | no" -whether to start the IKEv2 charon daemon or not. -The default is -.B yes -if starter was compiled with IKEv2 support. -.TP -.BR plutostart " = " yes " | no" -whether to start the IKEv1 pluto daemon or not. -The default is -.B yes -if starter was compiled with IKEv1 support. +.BR charondebug " = <debug list>" +how much charon debugging output should be logged. +A comma separated list containing type/level-pairs may +be specified, e.g: +.B dmn 3, ike 1, net -1. +Acceptable values for types are +.B dmn, mgr, ike, chd, job, cfg, knl, net, asn, enc, lib, esp, tls, +.B tnc, imc, imv, pts +and the level is one of +.B -1, 0, 1, 2, 3, 4 +(for silent, audit, control, controlmore, raw, private). By default, the level +is set to +.B 1 +for all types. For more flexibility see LOGGER CONFIGURATION in +.IR strongswan.conf (5). .TP .BR strictcrlpolicy " = yes | ifuri | " no defines if a fresh CRL must be available in order for the peer authentication @@ -1194,146 +1159,35 @@ if at least one CRL URI is defined and to .B no if no URI is known. .TP -.BR uniqueids " = " yes " | no | replace | keep" +.BR uniqueids " = " yes " | no | never | replace | keep" whether a particular participant ID should be kept unique, -with any new (automatically keyed) -connection using an ID from a different IP address -deemed to replace all old ones using that ID; +with any new IKE_SA using an ID deemed to replace all old ones using that ID; acceptable values are .B yes -(the default) +(the default), +.B no and -.BR no . -Participant IDs normally \fIare\fR unique, -so a new (automatically-keyed) connection using the same ID is -almost invariably intended to replace an old one. -The IKEv2 daemon also accepts the value +.BR never . +Participant IDs normally \fIare\fR unique, so a new IKE_SA using the same ID is +almost invariably intended to replace an old one. The difference between +.B no +and +.B never +is that the daemon will replace old IKE_SAs when receiving an INITIAL_CONTACT +notify if the option is +.B no +but will ignore these notifies if +.B never +is configured. +The daemon also accepts the value .B replace which is identical to .B yes and the value .B keep to reject new IKE_SA setups and keep the duplicate established earlier. -.PP -The following -.B config section -parameters are used by the IKEv1 Pluto daemon only: -.TP -.BR crlcheckinterval " = " 0s " | <time>" -interval in seconds. CRL fetching is enabled if the value is greater than zero. -Asynchronous, periodic checking for fresh CRLs is currently done by the -IKEv1 Pluto daemon only. -.TP -.BR keep_alive " = " 20s " | <time>" -interval in seconds between NAT keep alive packets, the default being 20 seconds. -.TP -.BR nat_traversal " = yes | " no -activates NAT traversal by accepting source ISAKMP ports different from udp/500 and -being able of floating to udp/4500 if a NAT situation is detected. -Accepted values are -.B yes -and -.B no -(the default). -Used by IKEv1 only, NAT traversal is always being active in IKEv2. -.TP -.BR nocrsend " = yes | " no -no certificate request payloads will be sent. -.TP -.BR pkcs11initargs " = <args>" -non-standard argument string for PKCS#11 C_Initialize() function; -required by NSS softoken. -.TP -.BR pkcs11module " = <args>" -defines the path to a dynamically loadable PKCS #11 library. -.TP -.BR pkcs11keepstate " = yes | " no -PKCS #11 login sessions will be kept during the whole lifetime of the keying -daemon. Useful with pin-pad smart card readers. -Accepted values are -.B yes -and -.B no -(the default). -.TP -.BR pkcs11proxy " = yes | " no -Pluto will act as a PKCS #11 proxy accessible via the whack interface. -Accepted values are -.B yes -and -.B no -(the default). -.TP -.BR plutodebug " = " none " | <debug list> | all" -how much pluto debugging output should be logged. -An empty value, -or the magic value -.BR none , -means no debugging output (the default). -The magic value -.B all -means full output. -Otherwise only the specified types of output -(a quoted list, names without the -.B \-\-debug\- -prefix, -separated by white space) are enabled; -for details on available debugging types, see -.IR pluto (8). -.TP -.BR plutostderrlog " = <file>" -Pluto will not use syslog, but rather log to stderr, and redirect stderr -to <file>. -.TP -.BR postpluto " = <command>" -shell command to run after starting pluto -(e.g., to remove a decrypted copy of the -.I ipsec.secrets -file). -It's run in a very simple way; -complexities like I/O redirection are best hidden within a script. -Any output is redirected for logging, -so running interactive commands is difficult unless they use -.I /dev/tty -or equivalent for their interaction. -Default is none. -.TP -.BR prepluto " = <command>" -shell command to run before starting pluto -(e.g., to decrypt an encrypted copy of the -.I ipsec.secrets -file). -It's run in a very simple way; -complexities like I/O redirection are best hidden within a script. -Any output is redirected for logging, -so running interactive commands is difficult unless they use -.I /dev/tty -or equivalent for their interaction. -Default is none. -.TP -.BR virtual_private " = <networks>" -defines private networks using a wildcard notation. -.PP -The following -.B config section -parameters are used by the IKEv2 charon daemon only: -.TP -.BR charondebug " = <debug list>" -how much charon debugging output should be logged. -A comma separated list containing type/level-pairs may -be specified, e.g: -.B dmn 3, ike 1, net -1. -Acceptable values for types are -.B dmn, mgr, ike, chd, job, cfg, knl, net, asn, enc, lib, tls, tnc, imc, imv, pts -and the level is one of -.B -1, 0, 1, 2, 3, 4 -(for silent, audit, control, controlmore, raw, private). By default, the level -is set to -.B 1 -for all types. For more flexibility see LOGGER CONFIGURATION in -.IR strongswan.conf (5). -.SH IKEv2 EXPIRY/REKEY +.SH SA EXPIRY/REKEY The IKE SAs and IPsec SAs negotiated by the daemon can be configured to expire after a specific amount of time. For IPsec SAs this can also happen after a specified number of transmitted packets or transmitted bytes. The following @@ -1419,12 +1273,8 @@ time equals zero and, thus, rekeying gets disabled. /etc/ipsec.d/crls .SH SEE ALSO -strongswan.conf(5), ipsec.secrets(5), ipsec(8), pluto(8) +strongswan.conf(5), ipsec.secrets(5), ipsec(8) .SH HISTORY Originally written for the FreeS/WAN project by Henry Spencer. Updated and extended for the strongSwan project <http://www.strongswan.org> by Tobias Brunner, Andreas Steffen and Martin Willi. -.SH BUGS -.PP -If conns are to be added before DNS is available, \fBleft=\fP\fIFQDN\fP -will fail. diff --git a/man/ipsec.conf.5.in b/man/ipsec.conf.5.in index ab255304d..4c64e86ca 100644 --- a/man/ipsec.conf.5.in +++ b/man/ipsec.conf.5.in @@ -1,4 +1,4 @@ -.TH IPSEC.CONF 5 "2011-12-14" "@IPSEC_VERSION@" "strongSwan" +.TH IPSEC.CONF 5 "2012-06-26" "@IPSEC_VERSION@" "strongSwan" .SH NAME ipsec.conf \- IPsec configuration and connections .SH DESCRIPTION @@ -172,9 +172,9 @@ keying, rekeying, and general control. The path to control the connection is called 'ISAKMP SA' in IKEv1 and 'IKE SA' in the IKEv2 protocol. That what is being negotiated, the kernel level data path, is called 'IPsec SA' or 'Child SA'. -strongSwan currently uses two separate keying daemons. \fIpluto\fP handles -all IKEv1 connections, \fIcharon\fP is the daemon handling the IKEv2 -protocol. +strongSwan previously used two separate keying daemons, \fIpluto\fP and +\fIcharon\fP. This manual does not discuss \fIpluto\fP options anymore, but +only \fIcharon\fP that since strongSwan 5.0 supports both IKEv1 and IKEv2. .PP To avoid trivial editing of the configuration file to suit it to each system involved in a connection, @@ -233,21 +233,14 @@ defines the identity of the AAA backend used during IKEv2 EAP authentication. This is required if the EAP client uses a method that verifies the server identity (such as EAP-TLS), but it does not match the IKEv2 gateway identity. .TP +.BR aggressive " = yes | " no +whether to use IKEv1 Aggressive or Main Mode (the default). +.TP .BR also " = <name>" includes conn section .BR <name> . .TP -.BR auth " = " esp " | ah" -whether authentication should be done as part of -ESP encryption, or separately using the AH protocol; -acceptable values are -.B esp -(the default) and -.BR ah . -.br -The IKEv2 daemon currently supports ESP only. -.TP -.BR authby " = " pubkey " | rsasig | ecdsasig | psk | eap | never | xauth..." +.BR authby " = " pubkey " | rsasig | ecdsasig | psk | secret | never | xauthpsk | xauthrsasig" how the two security gateways should authenticate each other; acceptable values are .B psk @@ -268,17 +261,12 @@ IKEv1 additionally supports the values .B xauthpsk and .B xauthrsasig -that will enable eXtended Authentication (XAuth) in addition to IKEv1 main mode -based on shared secrets or digital RSA signatures, respectively. -IKEv2 additionally supports the value -.BR eap , -which indicates an initiator to request EAP authentication. The EAP method -to use is selected by the server (see -.BR eap ). -This parameter is deprecated for IKEv2 connections, as two peers do not need -to agree on an authentication method. Use the +that will enable eXtended AUTHentication (XAUTH) in addition to IKEv1 main mode +based on shared secrets or digital RSA signatures, respectively. +This parameter is deprecated, as two peers do not need to agree on an +authentication method in IKEv2. Use the .B leftauth -parameter instead to define authentication methods in IKEv2. +parameter instead to define authentication methods. .TP .BR auto " = " ignore " | add | route | start" what operation, if any, should be done automatically at IPsec startup; @@ -295,18 +283,24 @@ loads a connection without starting it. loads a connection and installs kernel traps. If traffic is detected between .B leftsubnet and -.B rightsubnet -, a connection is established. +.BR rightsubnet , +a connection is established. .B start loads a connection and brings it up immediately. .B ignore -ignores the connection. This is equal to delete a connection from the config +ignores the connection. This is equal to deleting a connection from the config file. -Relevant only locally, other end need not agree on it -(but in general, for an intended-to-be-permanent connection, -both ends should use -.B auto=start -to ensure that any reboot causes immediate renegotiation). +Relevant only locally, other end need not agree on it. +.TP +.BR closeaction " = " none " | clear | hold | restart" +defines the action to take if the remote peer unexpectedly closes a CHILD_SA +(see +.B dpdaction +for meaning of values). +A +.B closeaction should not be +used if the peer uses reauthentication or uniquids checking, as these events +might trigger the defined action when not desired. .TP .BR compress " = yes | " no whether IPComp compression of content is proposed on the connection @@ -318,12 +312,11 @@ and .B no (the default). A value of .B yes -causes IPsec to propose both compressed and uncompressed, +causes the daemon to propose both compressed and uncompressed, and prefer compressed. A value of .B no -prevents IPsec from proposing compression; -a proposal to compress will still be accepted. +prevents the daemon from proposing or accepting compression. .TP .BR dpdaction " = " none " | clear | hold | restart" controls the use of the Dead Peer Detection protocol (DPD, RFC 3706) where @@ -341,16 +334,9 @@ put in the hold state .RB ( hold ) or restarted .RB ( restart ). -For IKEv1, the default is -.B none -which disables the active sending of R_U_THERE notifications. -Nevertheless pluto will always send the DPD Vendor ID during connection set up -in order to signal the readiness to act passively as a responder if the peer -wants to use DPD. For IKEv2, +The default is .B none -does't make sense, since all messages are used to detect dead peers. If specified, -it has the same meaning as the default -.RB ( clear ). +which disables the active sending of DPD messages. .TP .BR dpddelay " = " 30s " | <time>" defines the period time interval with which R_U_THERE messages/INFORMATIONAL @@ -359,58 +345,17 @@ received. In IKEv2, a value of 0 sends no additional INFORMATIONAL messages and uses only standard messages (such as those to rekey) to detect dead peers. .TP -.BR dpdtimeout " = " 150s " | <time>" +.BR dpdtimeout " = " 150s " | <time> defines the timeout interval, after which all connections to a peer are deleted in case of inactivity. This only applies to IKEv1, in IKEv2 the default retransmission timeout applies, as every exchange is used to detect dead peers. -See -.IR strongswan.conf (5) -for a description of the IKEv2 retransmission timeout. -.TP -.BR closeaction " = " none " | clear | hold | restart" -defines the action to take if the remote peer unexpectedly closes a CHILD_SA -(IKEv2 only, see dpdaction for meaning of values). A closeaction should not be -used if the peer uses reauthentication or uniquids checking, as these events -might trigger a closeaction when not desired. .TP .BR inactivity " = <time>" defines the timeout interval, after which a CHILD_SA is closed if it did -not send or receive any traffic. Currently supported in IKEv2 connections only. -.TP -.BR eap " = aka | ... | radius | ... | <type> | <type>-<vendor> -defines the EAP type to propose as server if the client requests EAP -authentication. Currently supported values are -.B aka -for EAP-AKA, -.B gtc -for EAP-GTC, -.B md5 -for EAP-MD5, -.B mschapv2 -for EAP-MS-CHAPv2, -.B peap -for EAP-PEAPv0, -.B radius -for the EAP-RADIUS proxy, -.B sim -for EAP-SIM, -.B tls -for EAP-TLS, and -.B ttls -for EAP-TTLSv0. -Additionally, IANA assigned EAP method numbers are accepted, or a -definition in the form -.B eap=type-vendor -(e.g. eap=7-12345) can be used to specify vendor specific EAP types. -This parameter is deprecated in the favour of -.B leftauth. - -To forward EAP authentication to a RADIUS server using the EAP-RADIUS plugin, -set -.BR eap=radius . +not send or receive any traffic. .TP .BR eap_identity " = <id>" -defines the identity the client uses to reply to a EAP Identity request. +defines the identity the client uses to reply to an EAP Identity request. If defined on the EAP server, the defined identity will be used as peer identity during EAP authentication. The special value .B %identity @@ -423,17 +368,17 @@ for the connection, e.g. .BR aes128-sha256 . The notation is .BR encryption-integrity[-dhgroup][-esnmode] . -.br + Defaults to -.BR aes128-sha1,3des-sha1 -for IKEv1. The IKEv2 daemon adds its extensive default proposal to this default +.BR aes128-sha1,3des-sha1 . +The daemon adds its extensive default proposal to this default or the configured value. To restrict it to the configured proposal an exclamation mark .RB ( ! ) can be added at the end. -.br + .BR Note : -As a responder both daemons accept the first supported proposal received from +As a responder the daemon accepts the first supported proposal received from the peer. In order to restrict a responder to only accept specific cipher suites, the strict flag .RB ( ! , @@ -441,8 +386,8 @@ exclamation mark) can be used, e.g: aes256-sha512-modp4096! .br If .B dh-group -is specified, CHILD_SA setup and rekeying include a separate Diffie-Hellman -exchange (IKEv2 only). Valid values for +is specified, CHILD_SA/Quick Mode setup and rekeying include a separate +Diffie-Hellman exchange. Valid values for .B esnmode (IKEv2 only) are .B esn @@ -455,39 +400,69 @@ the default is .BR forceencaps " = yes | " no force UDP encapsulation for ESP packets even if no NAT situation is detected. This may help to surmount restrictive firewalls. In order to force the peer to -encapsulate packets, NAT detection payloads are faked (IKEv2 only). +encapsulate packets, NAT detection payloads are faked. +.TP +.BR fragmentation " = yes | force | " no +whether to use IKE fragmentation (proprietary IKEv1 extension). Acceptable +values are +.BR yes , +.B force +and +.B no +(the default). Fragmented messages sent by a peer are always accepted +irrespective of the value of this option. If set to +.BR yes , +and the peer supports it, larger IKE messages will be sent in fragments. +If set to +.B force +the initial IKE message will already be fragmented if required. .TP .BR ike " = <cipher suites>" comma-separated list of IKE/ISAKMP SA encryption/authentication algorithms to be used, e.g. .BR aes128-sha1-modp2048 . The notation is -.BR encryption-integrity-dhgroup . -In IKEv2, multiple algorithms and proposals may be included, such as -aes128-aes256-sha1-modp1536-modp2048,3des-sha1-md5-modp1024. +.BR encryption-integrity[-prf]-dhgroup . +If no PRF is given, the algorithms defined for integrity are used for the PRF. +The prf keywords are the same as the integrity algorithms, but have a +.B prf +prefix (such as +.BR prfsha1 , +.B prfsha256 +or +.BR prfaesxcbc ). .br +In IKEv2, multiple algorithms and proposals may be included, such as +.BR aes128-aes256-sha1-modp1536-modp2048,3des-sha1-md5-modp1024 . + Defaults to -.B aes128-sha1-modp2048,3des-sha1-modp1536 -for IKEv1. The IKEv2 daemon adds its extensive default proposal to this +.BR aes128-sha1-modp2048,3des-sha1-modp1536 . +The daemon adds its extensive default proposal to this default or the configured value. To restrict it to the configured proposal an exclamation mark .RB ( ! ) can be added at the end. -.br + .BR Note : -As a responder both daemons accept the first supported proposal received from +As a responder the daemon accepts the first supported proposal received from the peer. In order to restrict a responder to only accept specific cipher suites, the strict flag -.BR ( ! , -exclamation mark) can be used, e.g: aes256-sha512-modp4096! +.RB ( ! , +exclamation mark) can be used, e.g: +.BR aes256-sha512-modp4096! +.TP +.BR ikedscp " = " 000000 " | <DSCP field>" +Differentiated Services Field Codepoint to set on outgoing IKE packets sent +from this connection. The value is a six digit binary encoded string defining +the Codepoint to set, as defined in RFC 2474. .TP .BR ikelifetime " = " 3h " | <time>" how long the keying channel of a connection (ISAKMP or IKE SA) should last before being renegotiated. Also see EXPIRY/REKEY below. .TP .BR installpolicy " = " yes " | no" -decides whether IPsec policies are installed in the kernel by the IKEv2 -charon daemon for a given connection. Allows peaceful cooperation e.g. with +decides whether IPsec policies are installed in the kernel by the charon daemon +for a given connection. Allows peaceful cooperation e.g. with the Mobile IPv6 daemon mip6d who wants to control the kernel policies. Acceptable values are .B yes @@ -495,21 +470,10 @@ Acceptable values are .BR no . .TP .BR keyexchange " = " ike " | ikev1 | ikev2" -method of key exchange; -which protocol should be used to initialize the connection. Connections marked with -.B ikev1 -are initiated with pluto, those marked with -.B ikev2 -with charon. An incoming request from the remote peer is handled by the correct -daemon, unaffected from the -.B keyexchange -setting. Starting with strongSwan 4.5 the default value +which key exchange protocol should be used to initiate the connection. +Connections marked with .B ike -is a synonym for -.BR ikev2 , -whereas in older strongSwan releases -.B ikev1 -was assumed. +use IKEv2 when initiating, but accept any protocol version when responding. .TP .BR keyingtries " = " 3 " | <number> | %forever" how many attempts (a whole number or \fB%forever\fP) should be made to @@ -524,45 +488,23 @@ Relevant only locally, other end need not agree on it. synonym for .BR lifetime . .TP -.BR left " = <ip address> | <fqdn> | %defaultroute | " %any +.BR left " = <ip address> | <fqdn> | " %any (required) the IP address of the left participant's public-network interface or one of several magic values. -If it is -.BR %defaultroute , -.B left -will be filled in automatically with the local address -of the default-route interface (as determined at IPsec startup time and -during configuration update). -Either -.B left -or -.B right -may be -.BR %defaultroute , -but not both. -The prefix -.B % -in front of a fully-qualified domain name or an IP address will implicitly set -.B leftallowany=yes. -If the domain name cannot be resolved into an IP address at IPsec startup or -update time then -.B left=%any -and -.B leftallowany=no -will be assumed. - -In case of an IKEv2 connection, the value +The value .B %any -for the local endpoint signifies an address to be filled in (by automatic -keying) during negotiation. If the local peer initiates the connection setup -the routing table will be queried to determine the correct local IP address. +(the default) for the local endpoint signifies an address to be filled in (by +automatic keying) during negotiation. If the local peer initiates the +connection setup the routing table will be queried to determine the correct +local IP address. In case the local peer is responding to a connection setup then any IP address that is assigned to a local interface will be accepted. -.br -Note that specifying -.B %any -for the local endpoint is not supported by the IKEv1 pluto daemon. + +The prefix +.B % +in front of a fully-qualified domain name or an IP address will implicitly set +.BR leftallowany =yes. If .B %any @@ -574,35 +516,37 @@ is used in that case. .TP .BR leftallowany " = yes | " no a modifier for -.B left -, making it behave as +.BR left , +making it behave as .B %any -although a concrete IP address has been assigned. -Recommended for dynamic IP addresses that can be resolved by DynDNS at IPsec -startup or update time. -Acceptable values are -.B yes -and -.B no -(the default). +although a concrete IP address or domain name has been assigned. .TP .BR leftauth " = <auth method>" Authentication method to use locally (left) or require from the remote (right) side. -This parameter is supported in IKEv2 only. Acceptable values are +Acceptable values are .B pubkey for public key authentication (RSA/ECDSA), .B psk -for pre-shared key authentication and +for pre-shared key authentication, .B eap -to (require the) use of the Extensible Authentication Protocol. +to (require the) use of the Extensible Authentication Protocol in IKEv2, and +.B xauth +for IKEv1 eXtended Authentication. To require a trustchain public key strength for the remote side, specify the -key type followed by the strength in bits (for example -.BR rsa-2048 +key type followed by the minimum strength in bits (for example +.BR ecdsa-384 +or +.BR rsa-2048-ecdsa-256 ). +To limit the acceptable set of hashing algorithms for trustchain validation, +append hash algorithms to +.BR pubkey +or a key strength definition (for example +.BR pubkey-sha1-sha256 or -.BR ecdsa-256 ). +.BR rsa-2048-ecdsa-256-sha256-sha384-sha512 ). For -.B eap, +.BR eap , an optional EAP method can be appended. Currently defined methods are .BR eap-aka , .BR eap-gtc , @@ -611,25 +555,41 @@ an optional EAP method can be appended. Currently defined methods are .BR eap-peap , .BR eap-sim , .BR eap-tls , +.BR eap-ttls , +.BR eap-dynamic , and -.BR eap-ttls . +.BR eap-radius . Alternatively, IANA assigned EAP method numbers are accepted. Vendor specific EAP methods are defined in the form .B eap-type-vendor .RB "(e.g. " eap-7-12345 ). +For +.B xauth, +an XAuth authentication backend can be specified, such as +.B xauth-generic +or +.BR xauth-eap . +If XAuth is used in +.BR leftauth , +Hybrid authentication is used. For traditional XAuth authentication, define +XAuth in +.BR lefauth2 . .TP .BR leftauth2 " = <auth method>" Same as .BR leftauth , -but defines an additional authentication exchange. IKEv2 supports multiple +but defines an additional authentication exchange. In IKEv1, only XAuth can be +used in the second authentication round. IKEv2 supports multiple complete authentication rounds using "Multiple Authentication Exchanges" defined -in RFC4739. This allows, for example, separated authentication -of host and user (IKEv2 only). +in RFC 4739. This allows, for example, separated authentication +of host and user. .TP .BR leftca " = <issuer dn> | %same" the distinguished name of a certificate authority which is required to lie in the trust path going from the left participant's certificate up to the root certification authority. +.B %same +means that the value configured for the right participant should be reused. .TP .BR leftca2 " = <issuer dn> | %same" Same as @@ -644,12 +604,23 @@ are accepted. By default .B leftcert sets .B leftid -to the distinguished name of the certificate's subject and -.B leftca -to the distinguished name of the certificate's issuer. +to the distinguished name of the certificate's subject. The left participant's ID can be overridden by specifying a .B leftid value which must be certified by the certificate, though. +.br +A value in the form +.B %smartcard[<slot nr>[@<module>]]:<keyid> +defines a specific certificate to load from a PKCS#11 backend for this +connection. See ipsec.secrets(5) for details about smartcard definitions. +.B leftcert +is required only if selecting the certificate with +.B leftid +is not sufficient, for example if multiple certificates use the same subject. +.br +Multiple certificate paths or PKCS#11 backends can be specified in a comma +separated list. The daemon chooses the certificate based on the received +certificate requests if possible before enforcing the first. .TP .BR leftcert2 " = <path>" Same as @@ -657,8 +628,17 @@ Same as but for the second authentication round (IKEv2 only). .TP .BR leftcertpolicy " = <OIDs>" -Comma separated list of certificate policy OIDs the peers certificate must have. -OIDs are specified using the numerical dotted representation (IKEv2 only). +Comma separated list of certificate policy OIDs the peer's certificate must +have. +OIDs are specified using the numerical dotted representation. +.TP +.BR leftdns " = <servers>" +Comma separated list of DNS server addresses to exchange as configuration +attributes. On the initiator, a server is a fixed IPv4/IPv6 address, or +.BR %config4 / %config6 +to request attributes without an address. On the responder, +only fixed IPv4/IPv6 addresses are allowed and define DNS servers assigned +to the client. .TP .BR leftfirewall " = yes | " no whether the left participant is doing forwarding-firewalling @@ -683,8 +663,7 @@ tunnels established with IPsec are exempted from it so that packets can flow unchanged through the tunnels. (This means that all subnets connected in this manner must have distinct, non-overlapping subnet address blocks.) -This is done by the default \fBipsec _updown\fR script (see -.IR pluto (8)). +This is done by the default \fBipsec _updown\fR script. In situations calling for more control, it may be preferable for the user to supply his own @@ -696,12 +675,13 @@ which makes the appropriate adjustments for his system. a comma separated list of group names. If the .B leftgroups parameter is present then the peer must be a member of at least one -of the groups defined by the parameter. Group membership must be certified -by a valid attribute certificate stored in \fI/etc/ipsec.d/acerts/\fP thas has -been issued to the peer by a trusted Authorization Authority stored in -\fI/etc/ipsec.d/aacerts/\fP. -.br -Attribute certificates are not supported in IKEv2 yet. +of the groups defined by the parameter. +.TP +.BR leftgroups2 " = <group list>" +Same as +.B leftgroups, +but for the second authentication round defined with +.B leftauth2. .TP .BR lefthostaccess " = yes | " no inserts a pair of INPUT and OUTPUT iptables rules using the default @@ -717,10 +697,25 @@ and .BR leftid " = <id>" how the left participant should be identified for authentication; defaults to -.BR left . -Can be an IP address or a fully-qualified domain name preceded by -.B @ -(which is used as a literal string and not resolved). +.B left +or the subject of the certificate configured with +.BR leftcert . +Can be an IP address, a fully-qualified domain name, an email address, or +a keyid. If +.B leftcert +is configured the identity has to be confirmed by the certificate. + +For IKEv2 and +.B rightid +the prefix +.B % +in front of the identity prevents the daemon from sending IDr in its IKE_AUTH +request and will allow it to verify the configured identity against the subject +and subjectAltNames contained in the responder's certificate (otherwise it is +only compared with the IDr returned by the responder). The IDr sent by the +initiator might otherwise prevent the responder from finding a config if it +has configured a different value for +.BR leftid . .TP .BR leftid2 " = <id>" identity to use for a second authentication for the left participant @@ -728,51 +723,30 @@ identity to use for a second authentication for the left participant .BR leftid . .TP .BR leftikeport " = <port>" -UDP port the left participant uses for IKE communication. Currently supported in -IKEv2 connections only. If unspecified, port 500 is used with the port floating +UDP port the left participant uses for IKE communication. +If unspecified, port 500 is used with the port floating to 4500 if a NAT is detected or MOBIKE is enabled. Specifying a local IKE port different from the default additionally requires a socket implementation that -listens to this port. -.TP -.BR leftnexthop " = %direct | %defaultroute | <ip address> | <fqdn>" -this parameter is usually not needed any more because the NETKEY IPsec stack -does not require explicit routing entries for the traffic to be tunneled. If -.B leftsourceip -is used with IKEv1 then -.B leftnexthop -must still be set in order for the source routes to work properly. +listens on this port. .TP .BR leftprotoport " = <protocol>/<port>" -restrict the traffic selector to a single protocol and/or port. -Examples: -.B leftprotoport=tcp/http +restrict the traffic selector to a single protocol and/or port. This option +is now deprecated, protocol/port information can be defined for each subnet +directly in +.BR leftsubnet . +.TP +.BR leftsigkey " = <raw public key> | <path to public key>" +the left participant's public key for public key signature authentication, +in PKCS#1 format using hex (0x prefix) or base64 (0s prefix) encoding. With the +optional +.B dns: or -.B leftprotoport=6/80 -or -.B leftprotoport=udp -.TP -.BR leftrsasigkey " = " %cert " | <raw rsa public key>" -the left participant's -public key for RSA signature authentication, -in RFC 2537 format using -.IR ttodata (3) +.B ssh: +prefix in front of 0x or 0s, the public key is expected to be in either +the RFC 3110 (not the full RR, only RSA key part) or RFC 4253 public key format, +respectively. +Also accepted is the path to a file containing the public key in PEM or DER encoding. -The magic value -.B %none -means the same as not specifying a value (useful to override a default). -The value -.B %cert -(the default) -means that the key is extracted from a certificate. -The identity used for the left participant -must be a specific host, not -.B %any -or another magic value. -.B Caution: -if two connection descriptions -specify different public keys for the same -.BR leftid , -confusion and madness will ensue. .TP .BR leftsendcert " = never | no | " ifasked " | always | yes" Accepted values are @@ -787,20 +761,25 @@ and the latter meaning that the peer must send a certificate request payload in order to get a certificate in return. .TP -.BR leftsourceip " = %config | %cfg | %modeconfig | %modecfg | <ip address>" -The internal source IP to use in a tunnel, also known as virtual IP. If the -value is one of the synonyms +.BR leftsourceip " = %config4 | %config6 | <ip address>" +Comma separated list of internal source IPs to use in a tunnel, also known as +virtual IP. If the value is one of the synonyms .BR %config , .BR %cfg , .BR %modeconfig , or .BR %modecfg , -an address is requested from the peer. In IKEv2, a statically defined address -is also requested, since the server may change it. +an address (from the tunnel address family) is requested from the peer. With +.B %config4 +and +.B %config6 +an address of the given address family will be requested explicitly. +If an IP address is configured, it will be requested from the responder, +which is free to respond with a different address. .TP .BR rightsourceip " = %config | <network>/<netmask> | %poolname" -The internal source IP to use in a tunnel for the remote peer. If the -value is +Comma separated list of internal source IPs to use in a tunnel for the remote +peer. If the value is .B %config on the responder side, the initiator must propose an address which is then echoed back. Also supported are address pools expressed as @@ -808,21 +787,47 @@ echoed back. Also supported are address pools expressed as or the use of an external IP address pool using %\fIpoolname\fR, where \fIpoolname\fR is the name of the IP address pool used for the lookup. .TP -.BR leftsubnet " = <ip subnet>" +.BR leftsubnet " = <ip subnet>[[<proto/port>]][,...]" private subnet behind the left participant, expressed as \fInetwork\fB/\fInetmask\fR; if omitted, essentially assumed to be \fIleft\fB/32\fR, signifying that the left end of the connection goes to the left participant -only. When using IKEv2, the configured subnet of the peers may differ, the -protocol narrows it to the greatest common subnet. Further, IKEv2 supports -multiple subnets separated by commas. IKEv1 only interprets the first subnet -of such a definition. -.TP -.BR leftsubnetwithin " = <ip subnet>" -the peer can propose any subnet or single IP address that fits within the -range defined by -.BR leftsubnetwithin. -Not relevant for IKEv2, as subnets are narrowed. +only. Configured subnets of the peers may differ, the protocol narrows it to +the greatest common subnet. In IKEv1, this may lead to problems with other +implementations, make sure to configure identical subnets in such +configurations. IKEv2 supports multiple subnets separated by commas. IKEv1 only +interprets the first subnet of such a definition, unless the Cisco Unity +extension plugin is enabled. + +The optional part after each subnet enclosed in square brackets specifies a +protocol/port to restrict the selector for that subnet. + +Examples: +.BR leftsubnet=10.0.0.1[tcp/http],10.0.0.2[6/80] " or" +.BR leftsubnet=fec1::1[udp],10.0.0.0/16[/53] . +Instead of omitting either value +.B %any +can be used to the same effect, e.g. +.BR leftsubnet=fec1::1[udp/%any],10.0.0.0/16[%any/53] . + +The port value can alternatively take the value +.B %opaque +for RFC 4301 OPAQUE selectors, or a numerical range in the form +.BR 1024-65535 . +None of the kernel backends currently supports opaque or port ranges and uses +.B %any +for policy installation instead. + +Instead of specifying a subnet, +.B %dynamic +can be used to replace it with the IKE address, having the same effect +as omitting +.B leftsubnet +completely. Using +.B %dynamic +can be used to define multiple dynamic selectors, each having a potentially +different protocol/port definition. + .TP .BR leftupdown " = <path>" what ``updown'' script to run to adjust routing and/or firewalling @@ -832,20 +837,15 @@ changes (default May include positional parameters separated by white space (although this requires enclosing the whole string in quotes); including shell metacharacters is unwise. -See -.IR pluto (8) -for details. -Relevant only locally, other end need not agree on it. IKEv2 uses the updown +Relevant only locally, other end need not agree on it. Charon uses the updown script to insert firewall rules only, since routing has been implemented -directly into charon. +directly into the daemon. .TP .BR lifebytes " = <number>" -the number of bytes transmitted over an IPsec SA before it expires (IKEv2 -only). +the number of bytes transmitted over an IPsec SA before it expires. .TP .BR lifepackets " = <number>" -the number of packets transmitted over an IPsec SA before it expires (IKEv2 -only). +the number of packets transmitted over an IPsec SA before it expires. .TP .BR lifetime " = " 1h " | <time>" how long a particular instance of a connection @@ -877,12 +877,12 @@ which thinks the lifetime is longer. Also see EXPIRY/REKEY below. .BR marginbytes " = <number>" how many bytes before IPsec SA expiry (see .BR lifebytes ) -should attempts to negotiate a replacement begin (IKEv2 only). +should attempts to negotiate a replacement begin. .TP .BR marginpackets " = <number>" how many packets before IPsec SA expiry (see .BR lifepackets ) -should attempts to negotiate a replacement begin (IKEv2 only). +should attempts to negotiate a replacement begin. .TP .BR margintime " = " 9m " | <time>" how long before connection expiry or keying-channel expiry @@ -921,7 +921,7 @@ enables the IKEv2 MOBIKE protocol defined by RFC 4555. Accepted values are .BR no . If set to .BR no , -the IKEv2 charon daemon will not actively propose MOBIKE as initiator and +the charon daemon will not actively propose MOBIKE as initiator and ignore the MOBIKE_SUPPORTED notify as responder. .TP .BR modeconfig " = push | " pull @@ -931,29 +931,8 @@ Accepted values are and .B pull (the default). -Currently relevant for IKEv1 only since IKEv2 always uses the configuration -payload in pull mode. Cisco VPN gateways usually operate in -.B push -mode. -.TP -.BR pfs " = " yes " | no" -whether Perfect Forward Secrecy of keys is desired on the connection's -keying channel -(with PFS, penetration of the key-exchange protocol -does not compromise keys negotiated earlier); -acceptable values are -.B yes -(the default) -and -.BR no. -IKEv2 always uses PFS for IKE_SA rekeying whereas for CHILD_SA rekeying -PFS is enforced by defining a Diffie-Hellman modp group in the -.B esp -parameter. -.TP -.BR pfsgroup " = <modp group>" -defines a Diffie-Hellman group for perfect forward secrecy in IKEv1 Quick Mode -differing from the DH group used for IKEv1 Main Mode (IKEv1 only). +Push mode is currently not supported in charon, hence this parameter has no +effect. .TP .BR reauth " = " yes " | no" whether rekeying of an IKE_SA should also reauthenticate the peer. In IKEv1, @@ -973,11 +952,12 @@ and .BR no . The two ends need not agree, but while a value of .B no -prevents pluto/charon from requesting renegotiation, +prevents charon from requesting renegotiation, it does not prevent responding to renegotiation requested from the other end, so .B no -will be largely ineffective unless both ends agree on it. +will be largely ineffective unless both ends agree on it. Also see +.BR reauth . .TP .BR rekeyfuzz " = " 100% " | <percentage>" maximum percentage by which @@ -1035,11 +1015,7 @@ signifying the special Mobile IPv6 transport proxy mode; .BR passthrough , signifying that no IPsec processing should be done at all; .BR drop , -signifying that packets should be discarded; and -.BR reject , -signifying that packets should be discarded and a diagnostic ICMP returned -.RB ( reject -is currently not supported by the NETKEY stack of the Linux 2.6 kernel). +signifying that packets should be discarded. .TP .BR xauth " = " client " | server" specifies the role in the XAuth protocol if activated by @@ -1105,6 +1081,11 @@ currently can have either the value .BR cacert " = <path>" defines a path to the CA certificate either relative to \fI/etc/ipsec.d/cacerts\fP or as an absolute path. +.br +A value in the form +.B %smartcard[<slot nr>[@<module>]]:<keyid> +defines a specific CA certificate to load from a PKCS#11 backend for this CA. +See ipsec.secrets(5) for details about smartcard definitions. .TP .BR crluri " = <uri>" defines a CRL distribution point (ldap, http, or file URI) @@ -1116,8 +1097,6 @@ synonym for .BR crluri2 " = <uri>" defines an alternative CRL distribution point (ldap, http, or file URI) .TP -.BR ldaphost " = <hostname>" -defines an ldap host. Currently used by IKEv1 only. .TP .BR ocspuri " = <uri>" defines an OCSP URI. @@ -1127,11 +1106,11 @@ synonym for .B ocspuri. .TP .BR ocspuri2 " = <uri>" -defines an alternative OCSP URI. Currently used by IKEv2 only. +defines an alternative OCSP URI. .TP .BR certuribase " = <uri>" defines the base URI for the Hash and URL feature supported by IKEv2. -Instead of exchanging complete certificates, IKEv2 allows to send an URI +Instead of exchanging complete certificates, IKEv2 allows one to send an URI that resolves to the DER encoded certificate. The certificate URIs are built by appending the SHA1 hash of the DER encoded certificates to this base URI. .SH "CONFIG SECTIONS" @@ -1140,48 +1119,34 @@ At present, the only section known to the IPsec software is the one named .BR setup , which contains information used when the software is being started. -Here's an example: -.PP -.ne 8 -.nf -.ft B -.ta 1c -config setup - plutodebug=all - crlcheckinterval=10m - strictcrlpolicy=yes -.ft -.fi -.PP -Parameters are optional unless marked ``(required)''. The currently-accepted .I parameter names in a .B config .B setup -section affecting both daemons are: +section are: .TP .BR cachecrls " = yes | " no -certificate revocation lists (CRLs) fetched via http or ldap will be cached in -\fI/etc/ipsec.d/crls/\fR under a unique file name derived from the certification -authority's public key. -Accepted values are -.B yes -and -.B no -(the default). Only relevant for IKEv1, as CRLs are always cached in IKEv2. +if enabled, certificate revocation lists (CRLs) fetched via HTTP or LDAP will +be cached in +.I /etc/ipsec.d/crls/ +under a unique file name derived from the certification authority's public key. .TP -.BR charonstart " = " yes " | no" -whether to start the IKEv2 charon daemon or not. -The default is -.B yes -if starter was compiled with IKEv2 support. -.TP -.BR plutostart " = " yes " | no" -whether to start the IKEv1 pluto daemon or not. -The default is -.B yes -if starter was compiled with IKEv1 support. +.BR charondebug " = <debug list>" +how much charon debugging output should be logged. +A comma separated list containing type/level-pairs may +be specified, e.g: +.B dmn 3, ike 1, net -1. +Acceptable values for types are +.B dmn, mgr, ike, chd, job, cfg, knl, net, asn, enc, lib, esp, tls, +.B tnc, imc, imv, pts +and the level is one of +.B -1, 0, 1, 2, 3, 4 +(for silent, audit, control, controlmore, raw, private). By default, the level +is set to +.B 1 +for all types. For more flexibility see LOGGER CONFIGURATION in +.IR strongswan.conf (5). .TP .BR strictcrlpolicy " = yes | ifuri | " no defines if a fresh CRL must be available in order for the peer authentication @@ -1194,146 +1159,35 @@ if at least one CRL URI is defined and to .B no if no URI is known. .TP -.BR uniqueids " = " yes " | no | replace | keep" +.BR uniqueids " = " yes " | no | never | replace | keep" whether a particular participant ID should be kept unique, -with any new (automatically keyed) -connection using an ID from a different IP address -deemed to replace all old ones using that ID; +with any new IKE_SA using an ID deemed to replace all old ones using that ID; acceptable values are .B yes -(the default) +(the default), +.B no and -.BR no . -Participant IDs normally \fIare\fR unique, -so a new (automatically-keyed) connection using the same ID is -almost invariably intended to replace an old one. -The IKEv2 daemon also accepts the value +.BR never . +Participant IDs normally \fIare\fR unique, so a new IKE_SA using the same ID is +almost invariably intended to replace an old one. The difference between +.B no +and +.B never +is that the daemon will replace old IKE_SAs when receiving an INITIAL_CONTACT +notify if the option is +.B no +but will ignore these notifies if +.B never +is configured. +The daemon also accepts the value .B replace which is identical to .B yes and the value .B keep to reject new IKE_SA setups and keep the duplicate established earlier. -.PP -The following -.B config section -parameters are used by the IKEv1 Pluto daemon only: -.TP -.BR crlcheckinterval " = " 0s " | <time>" -interval in seconds. CRL fetching is enabled if the value is greater than zero. -Asynchronous, periodic checking for fresh CRLs is currently done by the -IKEv1 Pluto daemon only. -.TP -.BR keep_alive " = " 20s " | <time>" -interval in seconds between NAT keep alive packets, the default being 20 seconds. -.TP -.BR nat_traversal " = yes | " no -activates NAT traversal by accepting source ISAKMP ports different from udp/500 and -being able of floating to udp/4500 if a NAT situation is detected. -Accepted values are -.B yes -and -.B no -(the default). -Used by IKEv1 only, NAT traversal is always being active in IKEv2. -.TP -.BR nocrsend " = yes | " no -no certificate request payloads will be sent. -.TP -.BR pkcs11initargs " = <args>" -non-standard argument string for PKCS#11 C_Initialize() function; -required by NSS softoken. -.TP -.BR pkcs11module " = <args>" -defines the path to a dynamically loadable PKCS #11 library. -.TP -.BR pkcs11keepstate " = yes | " no -PKCS #11 login sessions will be kept during the whole lifetime of the keying -daemon. Useful with pin-pad smart card readers. -Accepted values are -.B yes -and -.B no -(the default). -.TP -.BR pkcs11proxy " = yes | " no -Pluto will act as a PKCS #11 proxy accessible via the whack interface. -Accepted values are -.B yes -and -.B no -(the default). -.TP -.BR plutodebug " = " none " | <debug list> | all" -how much pluto debugging output should be logged. -An empty value, -or the magic value -.BR none , -means no debugging output (the default). -The magic value -.B all -means full output. -Otherwise only the specified types of output -(a quoted list, names without the -.B \-\-debug\- -prefix, -separated by white space) are enabled; -for details on available debugging types, see -.IR pluto (8). -.TP -.BR plutostderrlog " = <file>" -Pluto will not use syslog, but rather log to stderr, and redirect stderr -to <file>. -.TP -.BR postpluto " = <command>" -shell command to run after starting pluto -(e.g., to remove a decrypted copy of the -.I ipsec.secrets -file). -It's run in a very simple way; -complexities like I/O redirection are best hidden within a script. -Any output is redirected for logging, -so running interactive commands is difficult unless they use -.I /dev/tty -or equivalent for their interaction. -Default is none. -.TP -.BR prepluto " = <command>" -shell command to run before starting pluto -(e.g., to decrypt an encrypted copy of the -.I ipsec.secrets -file). -It's run in a very simple way; -complexities like I/O redirection are best hidden within a script. -Any output is redirected for logging, -so running interactive commands is difficult unless they use -.I /dev/tty -or equivalent for their interaction. -Default is none. -.TP -.BR virtual_private " = <networks>" -defines private networks using a wildcard notation. -.PP -The following -.B config section -parameters are used by the IKEv2 charon daemon only: -.TP -.BR charondebug " = <debug list>" -how much charon debugging output should be logged. -A comma separated list containing type/level-pairs may -be specified, e.g: -.B dmn 3, ike 1, net -1. -Acceptable values for types are -.B dmn, mgr, ike, chd, job, cfg, knl, net, asn, enc, lib, tls, tnc, imc, imv, pts -and the level is one of -.B -1, 0, 1, 2, 3, 4 -(for silent, audit, control, controlmore, raw, private). By default, the level -is set to -.B 1 -for all types. For more flexibility see LOGGER CONFIGURATION in -.IR strongswan.conf (5). -.SH IKEv2 EXPIRY/REKEY +.SH SA EXPIRY/REKEY The IKE SAs and IPsec SAs negotiated by the daemon can be configured to expire after a specific amount of time. For IPsec SAs this can also happen after a specified number of transmitted packets or transmitted bytes. The following @@ -1419,12 +1273,8 @@ time equals zero and, thus, rekeying gets disabled. /etc/ipsec.d/crls .SH SEE ALSO -strongswan.conf(5), ipsec.secrets(5), ipsec(8), pluto(8) +strongswan.conf(5), ipsec.secrets(5), ipsec(8) .SH HISTORY Originally written for the FreeS/WAN project by Henry Spencer. Updated and extended for the strongSwan project <http://www.strongswan.org> by Tobias Brunner, Andreas Steffen and Martin Willi. -.SH BUGS -.PP -If conns are to be added before DNS is available, \fBleft=\fP\fIFQDN\fP -will fail. diff --git a/man/ipsec.secrets.5 b/man/ipsec.secrets.5 index c7c092502..a4a58f261 100644 --- a/man/ipsec.secrets.5 +++ b/man/ipsec.secrets.5 @@ -1,4 +1,4 @@ -.TH IPSEC.SECRETS 5 "2011-12-14" "4.6.2dr3" "strongSwan" +.TH IPSEC.SECRETS 5 "2011-12-14" "5.1.0rc1" "strongSwan" .SH NAME ipsec.secrets \- secrets for IKE/IPsec authentication .SH DESCRIPTION @@ -37,13 +37,7 @@ by whitespace. If no ID selectors are specified the line must start with a colon. .LP A selector is an IP address, a Fully Qualified Domain Name, user@FQDN, -\fB%any\fP or \fB%any6\fP (other kinds may come). An IP address may be written -in the familiar dotted quad form or as a domain name to be looked up -when the file is loaded. -In many cases it is a bad idea to use domain names because -the name server may not be running or may be insecure. To denote a -Fully Qualified Domain Name (as opposed to an IP address denoted by -its domain name), precede the name with an at sign (\fB@\fP). +\fB%any\fP or \fB%any6\fP (other kinds may come). .LP Matching IDs with selectors is fairly straightforward: they have to be equal. In the case of a ``Road Warrior'' connection, if an equal @@ -97,9 +91,15 @@ defines an RSA private key .B ECDSA defines an ECDSA private key .TP +.B P12 +defines a PKCS#12 container +.TP .B EAP defines EAP credentials .TP +.B NTLM +defines NTLM credentials +.TP .B XAUTH defines XAUTH credentials .TP @@ -136,35 +136,49 @@ Similarly, a character sequence beginning with .B 0s is interpreted as Base64 encoded binary data. .TP -.B [ <selectors> ] : RSA <private key file> [ <passphrase> | %prompt ] +.B : RSA <private key file> [ <passphrase> | %prompt ] .TQ -.B [ <selectors> ] : ECDSA <private key file> [ <passphrase> | %prompt ] +.B : ECDSA <private key file> [ <passphrase> | %prompt ] For the private key file both absolute paths or paths relative to \fI/etc/ipsec.d/private\fP are accepted. If the private key file is encrypted, the \fIpassphrase\fP must be defined. Instead of a passphrase .B %prompt -can be used which then causes the daemons to ask the user for the password +can be used which then causes the daemon to ask the user for the password whenever it is required to decrypt the key. .TP +.B : P12 <PKCS#12 file> [ <passphrase> | %prompt ] +For the PKCS#12 file both absolute paths or paths relative to +\fI/etc/ipsec.d/private\fP are accepted. If the container is +encrypted, the \fIpassphrase\fP must be defined. Instead of a passphrase +.B %prompt +can be used which then causes the daemon to ask the user for the password +whenever it is required to decrypt the container. Private keys, client and CA +certificates are extracted from the container. To use such a client certificate +in a connection set leftid to one of the subjects of the certificate. +.TP .B <user id> : EAP <secret> The format of \fIsecret\fP is the same as that of \fBPSK\fP secrets. .br \fBEAP\fP secrets are IKEv2 only. .TP +.B <user id> : NTLM <secret> +The format of \fIsecret\fP is the same as that of \fBPSK\fP secrets, but the +secret is stored as NTLM hash, which is MD4(UTF-16LE(secret)), instead of as +cleartext. +.br +\fBNTLM\fP secrets can only be used with the \fBeap-mschapv2\fP plugin. +.TP .B [ <servername> ] <username> : XAUTH <password> The format of \fIpassword\fP is the same as that of \fBPSK\fP secrets. \fBXAUTH\fP secrets are IKEv1 only. .TP -.B : PIN <smartcard selector> <pin code> | %prompt -IKEv1 uses the format -.B "%smartcard[<slot nr>[:<key id>]]" -to specify the smartcard selector (e.g. %smartcard1:50). -The IKEv2 daemon supports multiple modules with the format -.B "%smartcard[<slot nr>[@<module>]]:<keyid>" -, but always requires a keyid to uniquely select the correct key. Instead of -specifying the pin code statically, +.B : PIN %smartcard[<slot nr>[@<module>]]:<keyid> <pin code> | %prompt +The smartcard selector always requires a keyid to uniquely select the correct +key. The slot number defines the slot on the token, the module name refers to +the module name defined in strongswan.conf(5). +Instead of specifying the pin code statically, .B %prompt -can be specified, which causes the daemons to ask the user for the pin code. +can be specified, which causes the daemon to ask the user for the pin code. .LP .SH FILES diff --git a/man/ipsec.secrets.5.in b/man/ipsec.secrets.5.in index aa1b5c9c1..ee20c9670 100644 --- a/man/ipsec.secrets.5.in +++ b/man/ipsec.secrets.5.in @@ -37,13 +37,7 @@ by whitespace. If no ID selectors are specified the line must start with a colon. .LP A selector is an IP address, a Fully Qualified Domain Name, user@FQDN, -\fB%any\fP or \fB%any6\fP (other kinds may come). An IP address may be written -in the familiar dotted quad form or as a domain name to be looked up -when the file is loaded. -In many cases it is a bad idea to use domain names because -the name server may not be running or may be insecure. To denote a -Fully Qualified Domain Name (as opposed to an IP address denoted by -its domain name), precede the name with an at sign (\fB@\fP). +\fB%any\fP or \fB%any6\fP (other kinds may come). .LP Matching IDs with selectors is fairly straightforward: they have to be equal. In the case of a ``Road Warrior'' connection, if an equal @@ -97,9 +91,15 @@ defines an RSA private key .B ECDSA defines an ECDSA private key .TP +.B P12 +defines a PKCS#12 container +.TP .B EAP defines EAP credentials .TP +.B NTLM +defines NTLM credentials +.TP .B XAUTH defines XAUTH credentials .TP @@ -136,35 +136,49 @@ Similarly, a character sequence beginning with .B 0s is interpreted as Base64 encoded binary data. .TP -.B [ <selectors> ] : RSA <private key file> [ <passphrase> | %prompt ] +.B : RSA <private key file> [ <passphrase> | %prompt ] .TQ -.B [ <selectors> ] : ECDSA <private key file> [ <passphrase> | %prompt ] +.B : ECDSA <private key file> [ <passphrase> | %prompt ] For the private key file both absolute paths or paths relative to \fI/etc/ipsec.d/private\fP are accepted. If the private key file is encrypted, the \fIpassphrase\fP must be defined. Instead of a passphrase .B %prompt -can be used which then causes the daemons to ask the user for the password +can be used which then causes the daemon to ask the user for the password whenever it is required to decrypt the key. .TP +.B : P12 <PKCS#12 file> [ <passphrase> | %prompt ] +For the PKCS#12 file both absolute paths or paths relative to +\fI/etc/ipsec.d/private\fP are accepted. If the container is +encrypted, the \fIpassphrase\fP must be defined. Instead of a passphrase +.B %prompt +can be used which then causes the daemon to ask the user for the password +whenever it is required to decrypt the container. Private keys, client and CA +certificates are extracted from the container. To use such a client certificate +in a connection set leftid to one of the subjects of the certificate. +.TP .B <user id> : EAP <secret> The format of \fIsecret\fP is the same as that of \fBPSK\fP secrets. .br \fBEAP\fP secrets are IKEv2 only. .TP +.B <user id> : NTLM <secret> +The format of \fIsecret\fP is the same as that of \fBPSK\fP secrets, but the +secret is stored as NTLM hash, which is MD4(UTF-16LE(secret)), instead of as +cleartext. +.br +\fBNTLM\fP secrets can only be used with the \fBeap-mschapv2\fP plugin. +.TP .B [ <servername> ] <username> : XAUTH <password> The format of \fIpassword\fP is the same as that of \fBPSK\fP secrets. \fBXAUTH\fP secrets are IKEv1 only. .TP -.B : PIN <smartcard selector> <pin code> | %prompt -IKEv1 uses the format -.B "%smartcard[<slot nr>[:<key id>]]" -to specify the smartcard selector (e.g. %smartcard1:50). -The IKEv2 daemon supports multiple modules with the format -.B "%smartcard[<slot nr>[@<module>]]:<keyid>" -, but always requires a keyid to uniquely select the correct key. Instead of -specifying the pin code statically, +.B : PIN %smartcard[<slot nr>[@<module>]]:<keyid> <pin code> | %prompt +The smartcard selector always requires a keyid to uniquely select the correct +key. The slot number defines the slot on the token, the module name refers to +the module name defined in strongswan.conf(5). +Instead of specifying the pin code statically, .B %prompt -can be specified, which causes the daemons to ask the user for the pin code. +can be specified, which causes the daemon to ask the user for the pin code. .LP .SH FILES diff --git a/man/strongswan.conf.5 b/man/strongswan.conf.5 index e56e786e0..fc99c8c47 100644 --- a/man/strongswan.conf.5 +++ b/man/strongswan.conf.5 @@ -1,4 +1,4 @@ -.TH STRONGSWAN.CONF 5 "2011-07-26" "4.6.4" "strongSwan" +.TH STRONGSWAN.CONF 5 "2013-07-22" "5.1.0" "strongSwan" .SH NAME strongswan.conf \- strongSwan configuration file .SH DESCRIPTION @@ -133,11 +133,20 @@ Path to database with file measurement information .TP .BR attest.load Plugins to load in ipsec attest tool + .SS charon section .TP +.BR Note : +Many of these options also apply to \fBcharon\-cmd\fR and other +\fBcharon\fR derivatives. Just use their respective name (e.g. +\fIcharon\-cmd\fR) instead of \fIcharon\fR. +.TP .BR charon.block_threshold " [5]" Maximum number of half-open IKE_SAs for a single peer IP .TP +.BR charon.cisco_unity " [no] +Send Cisco Unity vendor ID payload (IKEv1 only) +.TP .BR charon.close_ike_on_child_failure " [no]" Close the IKE_SA if setup of the CHILD_SA along with IKE_AUTH failed .TP @@ -156,7 +165,17 @@ Enable Denial of Service protection using cookies and aggressiveness checks Section to define file loggers, see LOGGER CONFIGURATION .TP .BR charon.flush_auth_cfg " [no]" - +If enabled objects used during authentication (certificates, identities etc.) +are released to free memory once an IKE_SA is established. +Enabling this might conflict with plugins that later need access to e.g. the +used certificates. +.TP +.BR charon.fragment_size " [512]" +Maximum size (in bytes) of a sent fragment when using the proprietary IKEv1 +fragmentation extension. +.TP +.BR charon.group +Name of the group the daemon changes to after startup .TP .BR charon.half_open_timeout " [30]" Timeout in seconds for connecting IKE_SAs (also see IKE_SA_INIT DROPPING). @@ -164,8 +183,17 @@ Timeout in seconds for connecting IKE_SAs (also see IKE_SA_INIT DROPPING). .BR charon.hash_and_url " [no]" Enable hash and URL support .TP +.BR charon.i_dont_care_about_security_and_use_aggressive_mode_psk " [no]" +If enabled responders are allowed to use IKEv1 Aggressive Mode with pre-shared +keys, which is discouraged due to security concerns (offline attacks on the +openly transmitted hash of the PSK) +.TP .BR charon.ignore_routing_tables -A list of routing tables to be excluded from route lookup +A space-separated list of routing tables to be excluded from route lookups +.TP +.BR charon.ikesa_limit " [0]" +Maximum number of IKE_SAs that can be established at the same time before new +connection attempts are blocked .TP .BR charon.ikesa_table_segments " [1]" Number of exclusively locked segments in the hash table @@ -184,12 +212,28 @@ IKE_SA_INIT DROPPING). Limit new connections based on the number of jobs currently queued for processing (see IKE_SA_INIT DROPPING). .TP +.BR charon.initiator_only " [no]" +Causes charon daemon to ignore IKE initiation requests. +.TP .BR charon.install_routes " [yes]" Install routes into a separate routing table for established IPsec tunnels .TP .BR charon.install_virtual_ip " [yes]" Install virtual IP addresses .TP +.BR charon.install_virtual_ip_on +The name of the interface on which virtual IP addresses should be installed. +If not specified the addresses will be installed on the outbound interface. +.TP +.BR charon.interfaces_ignore +A comma-separated list of network interfaces that should be ignored, if +.B charon.interfaces_use +is specified this option has no effect. +.TP +.BR charon.interfaces_use +A comma-separated list of network interfaces that should be used by charon. +All other interfaces are ignored. +.TP .BR charon.keep_alive " [20s]" NAT keep alive interval .TP @@ -207,11 +251,20 @@ Enable multiple authentication exchanges (RFC 4739) .BR charon.nbns2 WINS servers assigned to peer via configuration payload (CP) .TP +.BR charon.port " [500]" +UDP port used locally. If set to 0 a random port will be allocated. +.TP +.BR charon.port_nat_t " [4500]" +UDP port used locally in case of NAT-T. If set to 0 a random port will be +allocated. Has to be different from +.BR charon.port , +otherwise a random port will be allocated. +.TP .BR charon.process_route " [yes]" Process RTM_NEWROUTE and RTM_DELROUTE events .TP .BR charon.receive_delay " [0]" -Delay for receiving packets, to simulate larger RTT +Delay in ms for receiving packets, to simulate larger RTT .TP .BR charon.receive_delay_response " [yes]" Delay response messages @@ -234,6 +287,10 @@ Timeout in seconds before sending first retransmit .BR charon.retransmit_tries " [5]" Number of times to retransmit a packet before giving up .TP +.BR charon.retry_initiate_interval " [0]" +Interval to use when retrying to initiate an IKE_SA (e.g. if DNS resolution +failed), 0 to disable retries. +.TP .BR charon.reuse_ikesa " [yes] Initiate CHILD_SA within existing IKE_SAs .TP @@ -244,7 +301,7 @@ Numerical routing table to install routes to Priority of the routing table .TP .BR charon.send_delay " [0]" -Delay for sending packets, to simulate larger RTT +Delay in ms for sending packets, to simulate larger RTT .TP .BR charon.send_delay_response " [yes]" Delay response messages @@ -263,15 +320,59 @@ Section to define syslog loggers, see LOGGER CONFIGURATION .TP .BR charon.threads " [16]" Number of worker threads in charon +.TP +.BR charon.user +Name of the user the daemon changes to after startup .SS charon.plugins subsection .TP -.BR charon.plugins.android.loglevel " [1]" +.BR charon.plugins.android_log.loglevel " [1]" Loglevel for logging to Android specific logger .TP .BR charon.plugins.attr Section to specify arbitrary attributes that are assigned to a peer via configuration payload (CP) .TP +.BR charon.plugins.certexpire.csv.cron +Cron style string specifying CSV export times +.TP +.BR charon.plugins.certexpire.csv.empty_string +String to use in empty intermediate CA fields +.TP +.BR charon.plugins.certexpire.csv.fixed_fields " [yes]" +Use a fixed intermediate CA field count +.TP +.BR charon.plugins.certexpire.csv.force " [yes]" +Force export of all trustchains we have a private key for +.TP +.BR charon.plugins.certexpire.csv.format " [%d:%m:%Y]" +strftime(3) format string to export expiration dates as +.TP +.BR charon.plugins.certexpire.csv.local +strftime(3) format string for the CSV file name to export local certificates to +.TP +.BR charon.plugins.certexpire.csv.remote +strftime(3) format string for the CSV file name to export remote certificates to +.TP +.BR charon.plugins.certexpire.csv.separator " [,]" +CSV field separator +.TP +.BR charon.plugins.coupling.file +File to store coupling list to +.TP +.BR charon.plugins.coupling.hash " [sha1]" +Hashing algorithm to fingerprint coupled certificates +.TP +.BR charon.plugins.coupling.max " [1]" +Maximum number of coupling entries to create +.TP +.BR charon.plugins.dhcp.force_server_address " [no]" +Always use the configured server address. This might be helpful if the DHCP +server runs on the same host as strongSwan, and the DHCP daemon does not listen +on the loopback interface. In that case the server cannot be reached via +unicast (or even 255.255.255.255) as that would be routed via loopback. +Setting this option to yes and configuring the local broadcast address (e.g. +192.168.0.255) as server address might work. +.TP .BR charon.plugins.dhcp.identity_lease " [no]" Derive user-defined MAC address from hash of IKEv2 identity .TP @@ -279,7 +380,10 @@ Derive user-defined MAC address from hash of IKEv2 identity DHCP server unicast or broadcast IP address .TP .BR charon.plugins.duplicheck.enable " [yes]" -enable loaded duplicheck plugin +Enable duplicheck plugin (if loaded) +.TP +.BR charon.plugins.duplicheck.socket " [unix://${piddir}/charon.dck]" +Socket provided by the duplicheck plugin .TP .BR charon.plugins.eap-aka.request_identity " [yes]" @@ -287,15 +391,24 @@ enable loaded duplicheck plugin .BR charon.plugins.eap-aka-3ggp2.seq_check .TP -.BR charon.plugins.eap-gtc.pam_service " [login]" -PAM service to be used for authentication - +.BR charon.plugins.eap-dynamic.preferred +The preferred EAP method(s) to be used. If it is not given the first +registered method will be used initially. If a comma separated list is given +the methods are tried in the given order before trying the rest of the +registered methods. +.TP +.BR charon.plugins.eap-dynamic.prefer_user " [no]" +If enabled the EAP methods proposed in an EAP-Nak message sent by the peer are +preferred over the methods registered locally. +.TP +.BR charon.plugins.eap-gtc.backend " [pam]" +XAuth backend to be used for credential verification .TP .BR charon.plugins.eap-peap.fragment_size " [1024]" Maximum size of an EAP-PEAP packet .TP .BR charon.plugins.eap-peap.max_message_count " [32]" -Maximum number of processed EAP-PEAP packets +Maximum number of processed EAP-PEAP packets (0 = no limit) .TP .BR charon.plugins.eap-peap.include_length " [no]" Include length in non-fragmented EAP-PEAP packets @@ -311,11 +424,13 @@ Start phase2 EAP TNC protocol after successful client authentication .TP .BR charon.plugins.eap-peap.request_peer_auth " [no]" Request peer authentication based on a client certificate - .TP .BR charon.plugins.eap-radius.accounting " [no]" Send RADIUS accounting information to RADIUS servers. .TP +.BR charon.plugins.eap-radius.accounting_requires_vip " [no]" +If enabled, accounting is disabled unless an IKE_SA has at least one virtual IP +.TP .BR charon.plugins.eap-radius.class_group " [no]" Use the .I class @@ -325,6 +440,22 @@ is compared to the groups specified in the option in .B ipsec.conf (5). .TP +.BR charon.plugins.eap-radius.close_all_on_timeout " [no]" +Closes all IKE_SAs if communication with the RADIUS server times out. If it is +not set only the current IKE_SA is closed. +.TP +.BR charon.plugins.eap-radius.dae.enable " [no]" +Enables support for the Dynamic Authorization Extension (RFC 5176) +.TP +.BR charon.plugins.eap-radius.dae.listen " [0.0.0.0]" +Address to listen for DAE messages from the RADIUS server +.TP +.BR charon.plugins.eap-radius.dae.port " [3799]" +Port to listen for DAE requests +.TP +.BR charon.plugins.eap-radius.dae.secret +Shared secret used to verify/sign DAE messages +.TP .BR charon.plugins.eap-radius.eap_start " [no]" Send EAP-Start instead of EAP-Identity to start RADIUS conversation .TP @@ -341,6 +472,18 @@ is compared to the groups specified in the option in .B ipsec.conf (5). .TP +.BR charon.plugins.eap-radius.forward.ike_to_radius +RADIUS attributes to be forwarded from IKEv2 to RADIUS (can be defined by +name or attribute number, a colon can be used to specify vendor-specific +attributes, e.g. Reply-Message, or 11, or 36906:12). +.TP +.BR charon.plugins.eap-radius.forward.radius_to_ike +Same as +.B charon.plugins.eap-radius.forward.ike_to_radius +but from RADIUS to +IKEv2, a strongSwan specific private notify (40969) is used to transmit the +attributes. +.TP .BR charon.plugins.eap-radius.id_prefix Prefix to EAP-Identity, some AAA servers use a IMSI prefix to select the EAP method @@ -364,10 +507,15 @@ Section to specify multiple RADIUS servers. The .B sockets and .B port +(or +.BR auth_port ) options can be specified for each server. A server's IP/Hostname can be configured using the .B address -option. For each RADIUS server a priority can be specified using the +option. The +.BR acct_port " [1813]" +option can be used to specify the port used for RADIUS accounting. +For each RADIUS server a priority can be specified using the .BR preference " [0]" option. .TP @@ -380,32 +528,29 @@ Number of sockets (ports) to use, increase for high load .BR charon.plugins.eap-simaka-sql.database .TP -.BR charon.plugins.eap-simaka-sql.remove_used +.BR charon.plugins.eap-simaka-sql.remove_used " [no]" .TP .BR charon.plugins.eap-tls.fragment_size " [1024]" Maximum size of an EAP-TLS packet .TP .BR charon.plugins.eap-tls.max_message_count " [32]" -Maximum number of processed EAP-TLS packets +Maximum number of processed EAP-TLS packets (0 = no limit) .TP .BR charon.plugins.eap-tls.include_length " [yes]" Include length in non-fragmented EAP-TLS packets .TP -.BR charon.plugins.eap-tnc.fragment_size " [50000]" -Maximum size of an EAP-TNC packet -.TP .BR charon.plugins.eap-tnc.max_message_count " [10]" -Maximum number of processed EAP-TNC packets +Maximum number of processed EAP-TNC packets (0 = no limit) .TP -.BR charon.plugins.eap-tnc.include_length " [yes]" -Include length in non-fragmented EAP-TNC packets +.BR charon.plugins.eap-tnc.protocol " [tnccs-1.1]" +IF-TNCCS protocol version to be used (tnccs-1.1, tnccs-2.0, tnccs-dynamic) .TP .BR charon.plugins.eap-ttls.fragment_size " [1024]" Maximum size of an EAP-TTLS packet .TP .BR charon.plugins.eap-ttls.max_message_count " [32]" -Maximum number of processed EAP-TTLS packets +Maximum number of processed EAP-TTLS packets (0 = no limit) .TP .BR charon.plugins.eap-ttls.include_length " [yes]" Include length in non-fragmented EAP-TTLS packets @@ -422,6 +567,13 @@ Start phase2 EAP TNC protocol after successful client authentication .BR charon.plugins.eap-ttls.request_peer_auth " [no]" Request peer authentication based on a client certificate .TP +.BR charon.plugins.error-notify.socket " [unix://${piddir}/charon.enfy]" +Socket provided by the error-notify plugin +.TP +.BR charon.plugins.ha.autobalance " [0]" +Interval in seconds to automatically balance handled segments between nodes. +Set to 0 to disable. +.TP .BR charon.plugins.ha.fifo_interface " [yes]" .TP @@ -452,6 +604,9 @@ Request peer authentication based on a client certificate .BR charon.plugins.ha.segment_count " [1]" .TP +.BR charon.plugins.ipseckey.enable " [no]" +Enable the fetching of IPSECKEY RRs via DNS +.TP .BR charon.plugins.led.activity_led .TP @@ -464,9 +619,25 @@ Number of ipsecN devices .BR charon.plugins.kernel-klips.ipsec_dev_mtu " [0]" Set MTU of ipsecN device .TP +.BR charon.plugins.kernel-netlink.roam_events " [yes]" +Whether to trigger roam events when interfaces, addresses or routes change +.TP +.BR charon.plugins.kernel-pfroute.vip_wait " [1000]" +Time in ms to wait until virtual IP addresses appear/disappear before failing. +.TP .BR charon.plugins.load-tester Section to configure the load-tester plugin, see LOAD TESTS .TP +.BR charon.plugins.lookip.socket " [unix://${piddir}/charon.lkp]" +Socket provided by the lookip plugin +.TP +.BR charon.plugins.radattr.dir +Directory where RADIUS attributes are stored in client-ID specific files. +.TP +.BR charon.plugins.radattr.message_id " [-1]" +Attributes are added to all IKE_AUTH messages by default (-1), or only to the +IKE_AUTH message with the given IKEv2 message ID. +.TP .BR charon.plugins.resolve.file " [/etc/resolv.conf]" File where to add DNS server entries .TP @@ -476,6 +647,15 @@ is appended to this prefix to make it unique. The result has to be a valid interface name according to the rules defined by resolvconf. Also, it should have a high priority according to the order defined in interface-order(5). .TP +.BR charon.plugins.socket-default.set_source " [yes]" +Set source address on outbound packets, if possible. +.TP +.BR charon.plugins.socket-default.use_ipv4 " [yes]" +Listen on IPv4, if possible. +.TP +.BR charon.plugins.socket-default.use_ipv6 " [yes]" +Listen on IPv6, if possible. +.TP .BR charon.plugins.sql.database Database URI for charons SQL plugin .TP @@ -489,27 +669,63 @@ certificates even if they don't contain a CA basic constraint. .BR charon.plugins.stroke.max_concurrent " [4]" Maximum number of stroke messages handled concurrently .TP +.BR charon.plugins.stroke.socket " [unix://${piddir}/charon.ctl]" +Socket provided by the stroke plugin +.TP +.BR charon.plugins.stroke.timeout " [0]" +Timeout in ms for any stroke command. Use 0 to disable the timeout +.TP +.BR charon.plugins.systime-fix.interval " [0]" +Interval in seconds to check system time for validity. 0 disables the check +.TP +.BR charon.plugins.systime-fix.reauth " [no]" +Whether to use reauth or delete if an invalid cert lifetime is detected +.TP +.BR charon.plugins.systime-fix.threshold +Threshold date where system time is considered valid. Disabled if not specified +.TP +.BR charon.plugins.systime-fix.threshold_format " [%Y]" +strptime(3) format used to parse threshold option +.TP +.BR charon.plugins.tnccs-11.max_message_size " [45000]" +Maximum size of a PA-TNC message (XML & Base64 encoding) +.TP +.BR charon.plugins.tnccs-20.max_batch_size " [65522]" +Maximum size of a PB-TNC batch (upper limit via PT-EAP = 65529) +.TP +.BR charon.plugins.tnccs-20.max_message_size " [65490]" +Maximum size of a PA-TNC message (upper limit via PT-EAP = 65497) +.TP +.BR charon.plugins.tnc-ifmap.client_cert +Path to X.509 certificate file of IF-MAP client +.TP +.BR charon.plugins.tnc-ifmap.client_key +Path to private key file of IF-MAP client +.TP .BR charon.plugins.tnc-ifmap.device_name -Unique name of strongSwan as a PEP and/or PDP device +Unique name of strongSwan server as a PEP and/or PDP device .TP -.BR charon.plugins.tnc-ifmap.key_file -Concatenated client certificate and private key +.BR charon.plugins.tnc-ifmap.renew_session_interval " [150]" +Interval in seconds between periodic IF-MAP RenewSession requests .TP -.BR charon.plugins.tnc-ifmap.password -Authentication password of strongSwan MAP client +.BR charon.plugins.tnc-ifmap.server_uri " [https://localhost:8444/imap]" +URI of the form [https://]servername[:port][/path] .TP .BR charon.plugins.tnc-ifmap.server_cert -Certificate of MAP server +Path to X.509 certificate file of IF-MAP server .TP -.BR charon.plugins.tnc-ifmap.ssl_passphrase -Passphrase protecting the private key +.BR charon.plugins.tnc-ifmap.username_password +Credentials of IF-MAP client of the form username:password .TP -.BR charon.plugins.tnc-ifmap.username -Authentication username of strongSwan MAP client +.BR charon.plugins.tnc-imc.dlclose " [yes]" +Unload IMC after use .TP .BR charon.plugins.tnc-imc.preferred_language " [en]" Preferred language for TNC recommendations .TP +.BR charon.plugins.tnc-imv.dlclose " [yes]" +Unload IMV after use +.TP .BR charon.plugins.tnc-pdp.method " [ttls]" EAP tunnel method to be used .TP @@ -520,12 +736,32 @@ RADIUS server port the strongSwan PDP is listening on Shared RADIUS secret between strongSwan PDP and NAS .TP .BR charon.plugins.tnc-pdp.server -name of the strongSwan PDP as contained in the AAA certificate +Name of the strongSwan PDP as contained in the AAA certificate +.TP +.BR charon.plugins.tnc-pdp.timeout +Timeout in seconds before closing incomplete connections +.TP +.BR charon.plugins.updown.dns_handler " [no]" +Whether the updown script should handle DNS serves assigned via IKEv1 Mode +Config or IKEv2 Config Payloads (if enabled they can't be handled by other +plugins, like resolve) .TP .BR charon.plugins.whitelist.enable " [yes]" -enable loaded whitelist plugin +Enable loaded whitelist plugin +.TP +.BR charon.plugins.whitelist.socket " [unix://${piddir}/charon.wlst]" +Socket provided by the whitelist plugin +.TP +.BR charon.plugins.xauth-eap.backend " [radius]" +EAP plugin to be used as backend for XAuth credential verification +.TP +.BR charon.plugins.xauth-pam.pam_service " [login]" +PAM service to be used for authentication .SS libstrongswan section .TP +.BR libstrongswan.cert_cache " [yes]" +Whether relations in validated certificate chains should be cached in memory +.TP .BR libstrongswan.crypto_test.bench " [no]" .TP @@ -554,12 +790,24 @@ strength .BR libstrongswan.ecp_x_coordinate_only " [yes]" Compliance with the errata for RFC 4753 .TP +.BR libstrongswan.host_resolver.max_threads " [3]" +Maximum number of concurrent resolver threads (they are terminated if unused) +.TP +.BR libstrongswan.host_resolver.min_threads " [0]" +Minimum number of resolver threads to keep around +.TP .BR libstrongswan.integrity_test " [no]" Check daemon, libstrongswan and plugin integrity at startup .TP .BR libstrongswan.leak_detective.detailed " [yes]" Includes source file names and line numbers in leak detective output .TP +.BR libstrongswan.leak_detective.usage_threshold " [10240]" +Threshold in bytes for leaks to be reported (0 to report all) +.TP +.BR libstrongswan.leak_detective.usage_threshold_count " [0]" +Threshold in number of allocations for leaks to be reported (0 to report all) +.TP .BR libstrongswan.processor.priority_threads Subsection to configure the number of reserved threads per priority class see JOB PRIORITY MANAGEMENT @@ -569,7 +817,7 @@ Discard certificates with unsupported or unknown critical extensions .SS libstrongswan.plugins subsection .TP .BR libstrongswan.plugins.attr-sql.database -Database URI for attr-sql plugin used by charon and pluto +Database URI for attr-sql plugin used by charon .TP .BR libstrongswan.plugins.attr-sql.lease_history " [yes]" Enable logging of SQL IP pool leases @@ -580,9 +828,18 @@ Use faster random numbers in gcrypt; for testing only, produces weak keys! .BR libstrongswan.plugins.openssl.engine_id " [pkcs11]" ENGINE ID to use in the OpenSSL plugin .TP +.BR libstrongswan.plugins.openssl.fips_mode " [0]" +Set OpenSSL FIPS mode: disabled(0), enabled(1), Suite B enabled(2) +.TP .BR libstrongswan.plugins.pkcs11.modules List of available PKCS#11 modules .TP +.BR libstrongswan.plugins.pkcs11.load_certs " [yes]" +Whether to load certificates from tokens +.TP +.BR libstrongswan.plugins.pkcs11.reload_certs " [no]" +Reload certificates from all tokens if charon receives a SIGHUP +.TP .BR libstrongswan.plugins.pkcs11.use_dh " [no]" Whether the PKCS#11 modules should be used for DH and ECDH (see use_ecc option) .TP @@ -599,22 +856,63 @@ keys not stored on tokens .TP .BR libstrongswan.plugins.pkcs11.use_rng " [no]" Whether the PKCS#11 modules should be used as RNG +.TP +.BR libstrongswan.plugins.random.random " [/dev/random]" +File to read random bytes from, instead of /dev/random +.TP +.BR libstrongswan.plugins.random.urandom " [/dev/urandom]" +File to read pseudo random bytes from, instead of /dev/urandom +.TP +.BR libstrongswan.plugins.unbound.resolv_conf " [/etc/resolv.conf]" +File to read DNS resolver configuration from +.TP +.BR libstrongswan.plugins.unbound.trust_anchors " [/etc/ipsec.d/dnssec.keys]" +File to read DNSSEC trust anchors from (usually root zone KSK) +.SS libtls section +.TP +.BR libtls.cipher +List of TLS encryption ciphers +.TP +.BR libtls.key_exchange +List of TLS key exchange methods +.TP +.BR libtls.mac +List of TLS MAC algorithms +.TP +.BR libtls.suites +List of TLS cipher suites .SS libtnccs section .TP .BR libtnccs.tnc_config " [/etc/tnc_config]" TNC IMC/IMV configuration directory .SS libimcv section .TP +.BR libimcv.assessment_result " [yes]" +Whether IMVs send a standard IETF Assessment Result attribute +.TP +.BR libimcv.database +Global IMV policy database URI +.TP .BR libimcv.debug_level " [1]" Debug level for a stand-alone libimcv library .TP +.BR libimcv.load " [random nonce gmp pubkey x509]" +Plugins to load in IMC/IMVs +.TP +.BR libimcv.os_info.name +Manually set the name of the client OS (e.g. Ubuntu) +.TP +.BR libimcv.os_info.version +Manually set the version of the client OS (e.g. 12.04 i686) +.TP +.BR libimcv.policy_script " [ipsec _imv_policy]" +Script called for each TNC connection to generate IMV policies +.TP .BR libimcv.stderr_quiet " [no]" -Disable output to stderr with a stand-alone libimcv library +isable output to stderr with a stand-alone libimcv library +.PP .SS libimcv plugins section .TP -.BR libimcv.plugins.imc-attestation.platform_info -Information on operating system and hardware platform -.TP .BR libimcv.plugins.imc-attestation.aik_blob AIK encrypted private key blob file .TP @@ -633,9 +931,6 @@ Use Quote2 AIK signature instead of Quote signature .BR libimcv.plugins.imv-attestation.cadir Path to directory with AIK cacerts .TP -.BR libimcv.plugins.imv-attestation.database -Path to database with file measurement information -.TP .BR libimcv.plugins.imv-attestation.dh_group " [ecp256]" Preferred Diffie-Hellman group .TP @@ -645,17 +940,20 @@ Preferred measurement hash algorithm .BR libimcv.plugins.imv-attestation.min_nonce_len " [0]" DH minimum nonce length .TP -.BR libimcv.plugins.imv-attestation.platform_info -Information on operating system and hardware platform +.BR libimcv.plugins.imv-attestation.remediation_uri +URI pointing to attestation remediation instructions .TP -.BR libimcv.plugins.imv-scanner.closed_port_policy " [yes]" -By default all ports must be closed (yes) or can be open (no) +.BR libimcv.plugins.imc-os.push_info " [yes]" +Send operating system info without being prompted .TP -.BR libimcv.plugins.imv-scanner.tcp_ports -List of TCP ports that can be open or must be closed +.BR libimcv.plugins.imv-os.remediation_uri +URI pointing to operating system remediation instructions .TP -.BR libimcv.plugins.imv-scanner.udp_ports -List of UDP ports that can be open or must be closed +.BR libimcv.plugins.imc-scanner.push_info " [yes]" +Send open listening ports without being prompted +.TP +.BR libimcv.plugins.imv-scanner.remediation_uri +URI pointing to scanner remediation instructions .TP .BR libimcv.plugins.imc-test.additional_ids " [0]" Number of additional IMC IDs @@ -663,6 +961,12 @@ Number of additional IMC IDs .BR libimcv.plugins.imc-test.command " [none]" Command to be sent to the Test IMV .TP +.BR libimcv.plugins.imc-test.dummy_size " [0]" +Size of dummy attribute to be sent to the Test IMV (0 = disabled) +.TP +.BR libimcv.plugins.imv-test.remediation_uri +URI pointing to test remediation instructions +.TP .BR libimcv.plugins.imc-test.retry " [no]" Do a handshake retry .TP @@ -671,19 +975,6 @@ Command to be sent to the Test IMV in the handshake retry .TP .BR libimcv.plugins.imv-test.rounds " [0]" Number of IMC-IMV retry rounds -.SS libtls section -.TP -.BR libtls.cipher -List of TLS encryption ciphers -.TP -.BR libtls.key_exchange -List of TLS key exchange methods -.TP -.BR libtls.mac -List of TLS MAC algorithms -.TP -.BR libtls.suites -List of TLS cipher suites .SS manager section .TP .BR manager.database @@ -745,38 +1036,14 @@ Session timeout for mediation service .TP .BR openac.load Plugins to load in ipsec openac tool +.SS pacman section +.TP +.BR pacman.database +Database URI for the database that stores the package information .SS pki section .TP .BR pki.load Plugins to load in ipsec pki tool -.SS pluto section -.TP -.BR pluto.dns1 -.TQ -.BR pluto.dns2 -DNS servers assigned to peer via Mode Config -.TP -.BR pluto.load -Plugins to load in IKEv1 pluto daemon -.TP -.BR pluto.nbns1 -.TQ -.BR pluto.nbns2 -WINS servers assigned to peer via Mode Config -.TP -.BR pluto.threads " [4]" -Number of worker threads in pluto -.SS pluto.plugins section -.TP -.BR pluto.plugins.attr -Section to specify arbitrary attributes that are assigned to a peer via -Mode Config -.TP -.BR charon.plugins.kernel-klips.ipsec_dev_count " [4]" -Number of ipsecN devices -.TP -.BR charon.plugins.kernel-klips.ipsec_dev_mtu " [0]" -Set MTU of ipsecN device .SS pool section .TP .BR pool.load @@ -791,7 +1058,7 @@ Plugins to load in ipsec scepclient tool Plugins to load in starter .TP .BR starter.load_warning " [yes]" -Disable charon/pluto plugin load option warning +Disable charon plugin load option warning .SH LOGGER CONFIGURATION The options described below provide a much more flexible way to configure @@ -897,6 +1164,9 @@ Packet encoding/decoding encryption/decryption operations .B tls libtls library messages .TP +.B esp +libipsec library messages +.TP .B lib libstrongwan library messages .TP @@ -1104,7 +1374,7 @@ it within 30 seconds. Under high load, a higher value might be required. .SH LOAD TESTS To do stability testing and performance optimizations, the IKEv2 daemon charon -provides the load-tester plugin. This plugin allows to setup thousands of +provides the load-tester plugin. This plugin allows one to setup thousands of tunnels concurrently against the daemon itself or a remote host. .PP .B WARNING: @@ -1112,6 +1382,20 @@ Never enable the load-testing plugin on productive systems. It provides preconfigured credentials and allows an attacker to authenticate as any user. .SS Options .TP +.BR charon.plugins.load-tester.addrs +Subsection that contains key/value pairs with address pools (in CIDR notation) +to use for a specific network interface e.g. eth0 = 10.10.0.0/16 +.TP +.BR charon.plugins.load-tester.addrs_keep " [no]" +Whether to keep dynamic addresses even after the associated SA got terminated +.TP +.BR charon.plugins.load-tester.addrs_prefix " [16]" +Network prefix length to use when installing dynamic addresses. If set to -1 the +full address is used (i.e. 32 or 128) +.TP +.BR charon.plugins.load-tester.ca_dir +Directory to load (intermediate) CA certificates from +.TP .BR charon.plugins.load-tester.child_rekey " [600]" Seconds to start CHILD_SA rekeying after setup .TP @@ -1121,6 +1405,9 @@ Delay between initiatons for each thread .BR charon.plugins.load-tester.delete_after_established " [no]" Delete an IKE_SA as soon as it has been established .TP +.BR charon.plugins.load-tester.digest " [sha1]" +Digest algorithm used when issuing certificates +.TP .BR charon.plugins.load-tester.dpd_delay " [0]" DPD delay to use in load test .TP @@ -1133,6 +1420,9 @@ EAP secret to use in load test .BR charon.plugins.load-tester.enable " [no]" Enable the load testing plugin .TP +.BR charon.plugins.load-tester.esp " [aes128-sha1]" +CHILD_SA proposal to use for load tests +.TP .BR charon.plugins.load-tester.fake_kernel " [no]" Fake the kernel interface to allow load-testing against self .TP @@ -1142,6 +1432,9 @@ Seconds to start IKE_SA rekeying after setup .BR charon.plugins.load-tester.init_limit " [0]" Global limit of concurrently established SAs during load test .TP +.BR charon.plugins.load-tester.initiator " [0.0.0.0]" +Address to initiate from +.TP .BR charon.plugins.load-tester.initiators " [0]" Number of concurrent initiator threads to use in load test .TP @@ -1151,8 +1444,24 @@ Authentication method(s) the intiator uses .BR charon.plugins.load-tester.initiator_id Initiator ID used in load test .TP +.BR charon.plugins.load-tester.initiator_match +Initiator ID to match against as responder +.TP +.BR charon.plugins.load-tester.initiator_tsi +Traffic selector on initiator side, as proposed by initiator +.TP +.BR charon.plugins.load-tester.initiator_tsr +Traffic selector on responder side, as proposed by initiator +.TP .BR charon.plugins.load-tester.iterations " [1]" -Number of IKE_SAs to initate by each initiator in load test +Number of IKE_SAs to initiate by each initiator in load test +.TP +.BR charon.plugins.load-tester.issuer_cert +Path to the issuer certificate (if not configured a hard-coded value is used) +.TP +.BR charon.plugins.load-tester.issuer_key +Path to private key that is used to issue certificates (if not configured a +hard-coded value is used) .TP .BR charon.plugins.load-tester.pool Provide INTERNAL_IPV4_ADDRs from a named pool @@ -1163,7 +1472,7 @@ Preshared key to use in load test .BR charon.plugins.load-tester.proposal " [aes128-sha1-modp768]" IKE proposal to use in load test .TP -.BR charon.plugins.load-tester.remote " [127.0.0.1]" +.BR charon.plugins.load-tester.responder " [127.0.0.1]" Address to initiation connections to .TP .BR charon.plugins.load-tester.responder_auth " [pubkey]" @@ -1172,11 +1481,25 @@ Authentication method(s) the responder uses .BR charon.plugins.load-tester.responder_id Responder ID used in load test .TP +.BR charon.plugins.load-tester.responder_tsi " [initiator_tsi]" +Traffic selector on initiator side, as narrowed by responder +.TP +.BR charon.plugins.load-tester.responder_tsr " [initiator_tsr]" +Traffic selector on responder side, as narrowed by responder +.TP .BR charon.plugins.load-tester.request_virtual_ip " [no]" Request an INTERNAL_IPV4_ADDR from the server .TP .BR charon.plugins.load-tester.shutdown_when_complete " [no]" Shutdown the daemon after all IKE_SAs have been established +.TP +.BR charon.plugins.load-tester.socket " [unix://${piddir}/charon.ldt]" +Socket provided by the load-tester plugin +.TP +.BR charon.plugins.load-tester.version " [0]" +IKE version to use (0 means use IKEv2 as initiator and accept any version as +responder) +.PP .SS Configuration details For public key authentication, the responder uses the .B \(dqCN=srv, OU=load-test, O=strongSwan\(dq @@ -1211,7 +1534,7 @@ implementation called modpnull. By setting proposal = aes128-sha1-modpnull .EE this wicked fast DH implementation is used. It does not provide any security -at all, but allows to run tests without DH calculation overhead. +at all, but allows one to run tests without DH calculation overhead. .SS Examples .PP In the simplest case, the daemon initiates IKE_SAs against itself using the @@ -1255,9 +1578,9 @@ value if your box can not handle that much load, or decrease it to put more load on it. If the daemon starts retransmitting messages your box probably can not handle all connection attempts. .PP -The plugin also allows to test against a remote host. This might help to test -against a real world configuration. A connection setup to do stress testing of -a gateway might look like this: +The plugin also allows one to test against a remote host. This might help to +test against a real world configuration. A connection setup to do stress +testing of a gateway might look like this: .PP .EX charon { @@ -1332,7 +1655,8 @@ giving up 76s 165s /etc/strongswan.conf .SH SEE ALSO -ipsec.conf(5), ipsec.secrets(5), ipsec(8) +\fBipsec.conf\fR(5), \fBipsec.secrets\fR(5), \fBipsec\fR(8), \fBcharon-cmd\fR(8) + .SH HISTORY Written for the .UR http://www.strongswan.org diff --git a/man/strongswan.conf.5.in b/man/strongswan.conf.5.in index 05493ec75..847d9d520 100644 --- a/man/strongswan.conf.5.in +++ b/man/strongswan.conf.5.in @@ -1,4 +1,4 @@ -.TH STRONGSWAN.CONF 5 "2011-07-26" "@IPSEC_VERSION@" "strongSwan" +.TH STRONGSWAN.CONF 5 "2013-07-22" "@IPSEC_VERSION@" "strongSwan" .SH NAME strongswan.conf \- strongSwan configuration file .SH DESCRIPTION @@ -133,11 +133,20 @@ Path to database with file measurement information .TP .BR attest.load Plugins to load in ipsec attest tool + .SS charon section .TP +.BR Note : +Many of these options also apply to \fBcharon\-cmd\fR and other +\fBcharon\fR derivatives. Just use their respective name (e.g. +\fIcharon\-cmd\fR) instead of \fIcharon\fR. +.TP .BR charon.block_threshold " [5]" Maximum number of half-open IKE_SAs for a single peer IP .TP +.BR charon.cisco_unity " [no] +Send Cisco Unity vendor ID payload (IKEv1 only) +.TP .BR charon.close_ike_on_child_failure " [no]" Close the IKE_SA if setup of the CHILD_SA along with IKE_AUTH failed .TP @@ -156,7 +165,17 @@ Enable Denial of Service protection using cookies and aggressiveness checks Section to define file loggers, see LOGGER CONFIGURATION .TP .BR charon.flush_auth_cfg " [no]" - +If enabled objects used during authentication (certificates, identities etc.) +are released to free memory once an IKE_SA is established. +Enabling this might conflict with plugins that later need access to e.g. the +used certificates. +.TP +.BR charon.fragment_size " [512]" +Maximum size (in bytes) of a sent fragment when using the proprietary IKEv1 +fragmentation extension. +.TP +.BR charon.group +Name of the group the daemon changes to after startup .TP .BR charon.half_open_timeout " [30]" Timeout in seconds for connecting IKE_SAs (also see IKE_SA_INIT DROPPING). @@ -164,8 +183,17 @@ Timeout in seconds for connecting IKE_SAs (also see IKE_SA_INIT DROPPING). .BR charon.hash_and_url " [no]" Enable hash and URL support .TP +.BR charon.i_dont_care_about_security_and_use_aggressive_mode_psk " [no]" +If enabled responders are allowed to use IKEv1 Aggressive Mode with pre-shared +keys, which is discouraged due to security concerns (offline attacks on the +openly transmitted hash of the PSK) +.TP .BR charon.ignore_routing_tables -A list of routing tables to be excluded from route lookup +A space-separated list of routing tables to be excluded from route lookups +.TP +.BR charon.ikesa_limit " [0]" +Maximum number of IKE_SAs that can be established at the same time before new +connection attempts are blocked .TP .BR charon.ikesa_table_segments " [1]" Number of exclusively locked segments in the hash table @@ -184,12 +212,28 @@ IKE_SA_INIT DROPPING). Limit new connections based on the number of jobs currently queued for processing (see IKE_SA_INIT DROPPING). .TP +.BR charon.initiator_only " [no]" +Causes charon daemon to ignore IKE initiation requests. +.TP .BR charon.install_routes " [yes]" Install routes into a separate routing table for established IPsec tunnels .TP .BR charon.install_virtual_ip " [yes]" Install virtual IP addresses .TP +.BR charon.install_virtual_ip_on +The name of the interface on which virtual IP addresses should be installed. +If not specified the addresses will be installed on the outbound interface. +.TP +.BR charon.interfaces_ignore +A comma-separated list of network interfaces that should be ignored, if +.B charon.interfaces_use +is specified this option has no effect. +.TP +.BR charon.interfaces_use +A comma-separated list of network interfaces that should be used by charon. +All other interfaces are ignored. +.TP .BR charon.keep_alive " [20s]" NAT keep alive interval .TP @@ -207,11 +251,20 @@ Enable multiple authentication exchanges (RFC 4739) .BR charon.nbns2 WINS servers assigned to peer via configuration payload (CP) .TP +.BR charon.port " [500]" +UDP port used locally. If set to 0 a random port will be allocated. +.TP +.BR charon.port_nat_t " [4500]" +UDP port used locally in case of NAT-T. If set to 0 a random port will be +allocated. Has to be different from +.BR charon.port , +otherwise a random port will be allocated. +.TP .BR charon.process_route " [yes]" Process RTM_NEWROUTE and RTM_DELROUTE events .TP .BR charon.receive_delay " [0]" -Delay for receiving packets, to simulate larger RTT +Delay in ms for receiving packets, to simulate larger RTT .TP .BR charon.receive_delay_response " [yes]" Delay response messages @@ -234,6 +287,10 @@ Timeout in seconds before sending first retransmit .BR charon.retransmit_tries " [5]" Number of times to retransmit a packet before giving up .TP +.BR charon.retry_initiate_interval " [0]" +Interval to use when retrying to initiate an IKE_SA (e.g. if DNS resolution +failed), 0 to disable retries. +.TP .BR charon.reuse_ikesa " [yes] Initiate CHILD_SA within existing IKE_SAs .TP @@ -244,7 +301,7 @@ Numerical routing table to install routes to Priority of the routing table .TP .BR charon.send_delay " [0]" -Delay for sending packets, to simulate larger RTT +Delay in ms for sending packets, to simulate larger RTT .TP .BR charon.send_delay_response " [yes]" Delay response messages @@ -263,15 +320,59 @@ Section to define syslog loggers, see LOGGER CONFIGURATION .TP .BR charon.threads " [16]" Number of worker threads in charon +.TP +.BR charon.user +Name of the user the daemon changes to after startup .SS charon.plugins subsection .TP -.BR charon.plugins.android.loglevel " [1]" +.BR charon.plugins.android_log.loglevel " [1]" Loglevel for logging to Android specific logger .TP .BR charon.plugins.attr Section to specify arbitrary attributes that are assigned to a peer via configuration payload (CP) .TP +.BR charon.plugins.certexpire.csv.cron +Cron style string specifying CSV export times +.TP +.BR charon.plugins.certexpire.csv.empty_string +String to use in empty intermediate CA fields +.TP +.BR charon.plugins.certexpire.csv.fixed_fields " [yes]" +Use a fixed intermediate CA field count +.TP +.BR charon.plugins.certexpire.csv.force " [yes]" +Force export of all trustchains we have a private key for +.TP +.BR charon.plugins.certexpire.csv.format " [%d:%m:%Y]" +strftime(3) format string to export expiration dates as +.TP +.BR charon.plugins.certexpire.csv.local +strftime(3) format string for the CSV file name to export local certificates to +.TP +.BR charon.plugins.certexpire.csv.remote +strftime(3) format string for the CSV file name to export remote certificates to +.TP +.BR charon.plugins.certexpire.csv.separator " [,]" +CSV field separator +.TP +.BR charon.plugins.coupling.file +File to store coupling list to +.TP +.BR charon.plugins.coupling.hash " [sha1]" +Hashing algorithm to fingerprint coupled certificates +.TP +.BR charon.plugins.coupling.max " [1]" +Maximum number of coupling entries to create +.TP +.BR charon.plugins.dhcp.force_server_address " [no]" +Always use the configured server address. This might be helpful if the DHCP +server runs on the same host as strongSwan, and the DHCP daemon does not listen +on the loopback interface. In that case the server cannot be reached via +unicast (or even 255.255.255.255) as that would be routed via loopback. +Setting this option to yes and configuring the local broadcast address (e.g. +192.168.0.255) as server address might work. +.TP .BR charon.plugins.dhcp.identity_lease " [no]" Derive user-defined MAC address from hash of IKEv2 identity .TP @@ -279,7 +380,10 @@ Derive user-defined MAC address from hash of IKEv2 identity DHCP server unicast or broadcast IP address .TP .BR charon.plugins.duplicheck.enable " [yes]" -enable loaded duplicheck plugin +Enable duplicheck plugin (if loaded) +.TP +.BR charon.plugins.duplicheck.socket " [unix://${piddir}/charon.dck]" +Socket provided by the duplicheck plugin .TP .BR charon.plugins.eap-aka.request_identity " [yes]" @@ -287,15 +391,24 @@ enable loaded duplicheck plugin .BR charon.plugins.eap-aka-3ggp2.seq_check .TP -.BR charon.plugins.eap-gtc.pam_service " [login]" -PAM service to be used for authentication - +.BR charon.plugins.eap-dynamic.preferred +The preferred EAP method(s) to be used. If it is not given the first +registered method will be used initially. If a comma separated list is given +the methods are tried in the given order before trying the rest of the +registered methods. +.TP +.BR charon.plugins.eap-dynamic.prefer_user " [no]" +If enabled the EAP methods proposed in an EAP-Nak message sent by the peer are +preferred over the methods registered locally. +.TP +.BR charon.plugins.eap-gtc.backend " [pam]" +XAuth backend to be used for credential verification .TP .BR charon.plugins.eap-peap.fragment_size " [1024]" Maximum size of an EAP-PEAP packet .TP .BR charon.plugins.eap-peap.max_message_count " [32]" -Maximum number of processed EAP-PEAP packets +Maximum number of processed EAP-PEAP packets (0 = no limit) .TP .BR charon.plugins.eap-peap.include_length " [no]" Include length in non-fragmented EAP-PEAP packets @@ -311,11 +424,13 @@ Start phase2 EAP TNC protocol after successful client authentication .TP .BR charon.plugins.eap-peap.request_peer_auth " [no]" Request peer authentication based on a client certificate - .TP .BR charon.plugins.eap-radius.accounting " [no]" Send RADIUS accounting information to RADIUS servers. .TP +.BR charon.plugins.eap-radius.accounting_requires_vip " [no]" +If enabled, accounting is disabled unless an IKE_SA has at least one virtual IP +.TP .BR charon.plugins.eap-radius.class_group " [no]" Use the .I class @@ -325,6 +440,22 @@ is compared to the groups specified in the option in .B ipsec.conf (5). .TP +.BR charon.plugins.eap-radius.close_all_on_timeout " [no]" +Closes all IKE_SAs if communication with the RADIUS server times out. If it is +not set only the current IKE_SA is closed. +.TP +.BR charon.plugins.eap-radius.dae.enable " [no]" +Enables support for the Dynamic Authorization Extension (RFC 5176) +.TP +.BR charon.plugins.eap-radius.dae.listen " [0.0.0.0]" +Address to listen for DAE messages from the RADIUS server +.TP +.BR charon.plugins.eap-radius.dae.port " [3799]" +Port to listen for DAE requests +.TP +.BR charon.plugins.eap-radius.dae.secret +Shared secret used to verify/sign DAE messages +.TP .BR charon.plugins.eap-radius.eap_start " [no]" Send EAP-Start instead of EAP-Identity to start RADIUS conversation .TP @@ -341,6 +472,18 @@ is compared to the groups specified in the option in .B ipsec.conf (5). .TP +.BR charon.plugins.eap-radius.forward.ike_to_radius +RADIUS attributes to be forwarded from IKEv2 to RADIUS (can be defined by +name or attribute number, a colon can be used to specify vendor-specific +attributes, e.g. Reply-Message, or 11, or 36906:12). +.TP +.BR charon.plugins.eap-radius.forward.radius_to_ike +Same as +.B charon.plugins.eap-radius.forward.ike_to_radius +but from RADIUS to +IKEv2, a strongSwan specific private notify (40969) is used to transmit the +attributes. +.TP .BR charon.plugins.eap-radius.id_prefix Prefix to EAP-Identity, some AAA servers use a IMSI prefix to select the EAP method @@ -364,10 +507,15 @@ Section to specify multiple RADIUS servers. The .B sockets and .B port +(or +.BR auth_port ) options can be specified for each server. A server's IP/Hostname can be configured using the .B address -option. For each RADIUS server a priority can be specified using the +option. The +.BR acct_port " [1813]" +option can be used to specify the port used for RADIUS accounting. +For each RADIUS server a priority can be specified using the .BR preference " [0]" option. .TP @@ -380,32 +528,29 @@ Number of sockets (ports) to use, increase for high load .BR charon.plugins.eap-simaka-sql.database .TP -.BR charon.plugins.eap-simaka-sql.remove_used +.BR charon.plugins.eap-simaka-sql.remove_used " [no]" .TP .BR charon.plugins.eap-tls.fragment_size " [1024]" Maximum size of an EAP-TLS packet .TP .BR charon.plugins.eap-tls.max_message_count " [32]" -Maximum number of processed EAP-TLS packets +Maximum number of processed EAP-TLS packets (0 = no limit) .TP .BR charon.plugins.eap-tls.include_length " [yes]" Include length in non-fragmented EAP-TLS packets .TP -.BR charon.plugins.eap-tnc.fragment_size " [50000]" -Maximum size of an EAP-TNC packet -.TP .BR charon.plugins.eap-tnc.max_message_count " [10]" -Maximum number of processed EAP-TNC packets +Maximum number of processed EAP-TNC packets (0 = no limit) .TP -.BR charon.plugins.eap-tnc.include_length " [yes]" -Include length in non-fragmented EAP-TNC packets +.BR charon.plugins.eap-tnc.protocol " [tnccs-1.1]" +IF-TNCCS protocol version to be used (tnccs-1.1, tnccs-2.0, tnccs-dynamic) .TP .BR charon.plugins.eap-ttls.fragment_size " [1024]" Maximum size of an EAP-TTLS packet .TP .BR charon.plugins.eap-ttls.max_message_count " [32]" -Maximum number of processed EAP-TTLS packets +Maximum number of processed EAP-TTLS packets (0 = no limit) .TP .BR charon.plugins.eap-ttls.include_length " [yes]" Include length in non-fragmented EAP-TTLS packets @@ -422,6 +567,13 @@ Start phase2 EAP TNC protocol after successful client authentication .BR charon.plugins.eap-ttls.request_peer_auth " [no]" Request peer authentication based on a client certificate .TP +.BR charon.plugins.error-notify.socket " [unix://${piddir}/charon.enfy]" +Socket provided by the error-notify plugin +.TP +.BR charon.plugins.ha.autobalance " [0]" +Interval in seconds to automatically balance handled segments between nodes. +Set to 0 to disable. +.TP .BR charon.plugins.ha.fifo_interface " [yes]" .TP @@ -452,6 +604,9 @@ Request peer authentication based on a client certificate .BR charon.plugins.ha.segment_count " [1]" .TP +.BR charon.plugins.ipseckey.enable " [no]" +Enable the fetching of IPSECKEY RRs via DNS +.TP .BR charon.plugins.led.activity_led .TP @@ -464,9 +619,25 @@ Number of ipsecN devices .BR charon.plugins.kernel-klips.ipsec_dev_mtu " [0]" Set MTU of ipsecN device .TP +.BR charon.plugins.kernel-netlink.roam_events " [yes]" +Whether to trigger roam events when interfaces, addresses or routes change +.TP +.BR charon.plugins.kernel-pfroute.vip_wait " [1000]" +Time in ms to wait until virtual IP addresses appear/disappear before failing. +.TP .BR charon.plugins.load-tester Section to configure the load-tester plugin, see LOAD TESTS .TP +.BR charon.plugins.lookip.socket " [unix://${piddir}/charon.lkp]" +Socket provided by the lookip plugin +.TP +.BR charon.plugins.radattr.dir +Directory where RADIUS attributes are stored in client-ID specific files. +.TP +.BR charon.plugins.radattr.message_id " [-1]" +Attributes are added to all IKE_AUTH messages by default (-1), or only to the +IKE_AUTH message with the given IKEv2 message ID. +.TP .BR charon.plugins.resolve.file " [/etc/resolv.conf]" File where to add DNS server entries .TP @@ -476,6 +647,15 @@ is appended to this prefix to make it unique. The result has to be a valid interface name according to the rules defined by resolvconf. Also, it should have a high priority according to the order defined in interface-order(5). .TP +.BR charon.plugins.socket-default.set_source " [yes]" +Set source address on outbound packets, if possible. +.TP +.BR charon.plugins.socket-default.use_ipv4 " [yes]" +Listen on IPv4, if possible. +.TP +.BR charon.plugins.socket-default.use_ipv6 " [yes]" +Listen on IPv6, if possible. +.TP .BR charon.plugins.sql.database Database URI for charons SQL plugin .TP @@ -489,27 +669,63 @@ certificates even if they don't contain a CA basic constraint. .BR charon.plugins.stroke.max_concurrent " [4]" Maximum number of stroke messages handled concurrently .TP +.BR charon.plugins.stroke.socket " [unix://${piddir}/charon.ctl]" +Socket provided by the stroke plugin +.TP +.BR charon.plugins.stroke.timeout " [0]" +Timeout in ms for any stroke command. Use 0 to disable the timeout +.TP +.BR charon.plugins.systime-fix.interval " [0]" +Interval in seconds to check system time for validity. 0 disables the check +.TP +.BR charon.plugins.systime-fix.reauth " [no]" +Whether to use reauth or delete if an invalid cert lifetime is detected +.TP +.BR charon.plugins.systime-fix.threshold +Threshold date where system time is considered valid. Disabled if not specified +.TP +.BR charon.plugins.systime-fix.threshold_format " [%Y]" +strptime(3) format used to parse threshold option +.TP +.BR charon.plugins.tnccs-11.max_message_size " [45000]" +Maximum size of a PA-TNC message (XML & Base64 encoding) +.TP +.BR charon.plugins.tnccs-20.max_batch_size " [65522]" +Maximum size of a PB-TNC batch (upper limit via PT-EAP = 65529) +.TP +.BR charon.plugins.tnccs-20.max_message_size " [65490]" +Maximum size of a PA-TNC message (upper limit via PT-EAP = 65497) +.TP +.BR charon.plugins.tnc-ifmap.client_cert +Path to X.509 certificate file of IF-MAP client +.TP +.BR charon.plugins.tnc-ifmap.client_key +Path to private key file of IF-MAP client +.TP .BR charon.plugins.tnc-ifmap.device_name -Unique name of strongSwan as a PEP and/or PDP device +Unique name of strongSwan server as a PEP and/or PDP device .TP -.BR charon.plugins.tnc-ifmap.key_file -Concatenated client certificate and private key +.BR charon.plugins.tnc-ifmap.renew_session_interval " [150]" +Interval in seconds between periodic IF-MAP RenewSession requests .TP -.BR charon.plugins.tnc-ifmap.password -Authentication password of strongSwan MAP client +.BR charon.plugins.tnc-ifmap.server_uri " [https://localhost:8444/imap]" +URI of the form [https://]servername[:port][/path] .TP .BR charon.plugins.tnc-ifmap.server_cert -Certificate of MAP server +Path to X.509 certificate file of IF-MAP server .TP -.BR charon.plugins.tnc-ifmap.ssl_passphrase -Passphrase protecting the private key +.BR charon.plugins.tnc-ifmap.username_password +Credentials of IF-MAP client of the form username:password .TP -.BR charon.plugins.tnc-ifmap.username -Authentication username of strongSwan MAP client +.BR charon.plugins.tnc-imc.dlclose " [yes]" +Unload IMC after use .TP .BR charon.plugins.tnc-imc.preferred_language " [en]" Preferred language for TNC recommendations .TP +.BR charon.plugins.tnc-imv.dlclose " [yes]" +Unload IMV after use +.TP .BR charon.plugins.tnc-pdp.method " [ttls]" EAP tunnel method to be used .TP @@ -520,12 +736,32 @@ RADIUS server port the strongSwan PDP is listening on Shared RADIUS secret between strongSwan PDP and NAS .TP .BR charon.plugins.tnc-pdp.server -name of the strongSwan PDP as contained in the AAA certificate +Name of the strongSwan PDP as contained in the AAA certificate +.TP +.BR charon.plugins.tnc-pdp.timeout +Timeout in seconds before closing incomplete connections +.TP +.BR charon.plugins.updown.dns_handler " [no]" +Whether the updown script should handle DNS serves assigned via IKEv1 Mode +Config or IKEv2 Config Payloads (if enabled they can't be handled by other +plugins, like resolve) .TP .BR charon.plugins.whitelist.enable " [yes]" -enable loaded whitelist plugin +Enable loaded whitelist plugin +.TP +.BR charon.plugins.whitelist.socket " [unix://${piddir}/charon.wlst]" +Socket provided by the whitelist plugin +.TP +.BR charon.plugins.xauth-eap.backend " [radius]" +EAP plugin to be used as backend for XAuth credential verification +.TP +.BR charon.plugins.xauth-pam.pam_service " [login]" +PAM service to be used for authentication .SS libstrongswan section .TP +.BR libstrongswan.cert_cache " [yes]" +Whether relations in validated certificate chains should be cached in memory +.TP .BR libstrongswan.crypto_test.bench " [no]" .TP @@ -554,12 +790,24 @@ strength .BR libstrongswan.ecp_x_coordinate_only " [yes]" Compliance with the errata for RFC 4753 .TP +.BR libstrongswan.host_resolver.max_threads " [3]" +Maximum number of concurrent resolver threads (they are terminated if unused) +.TP +.BR libstrongswan.host_resolver.min_threads " [0]" +Minimum number of resolver threads to keep around +.TP .BR libstrongswan.integrity_test " [no]" Check daemon, libstrongswan and plugin integrity at startup .TP .BR libstrongswan.leak_detective.detailed " [yes]" Includes source file names and line numbers in leak detective output .TP +.BR libstrongswan.leak_detective.usage_threshold " [10240]" +Threshold in bytes for leaks to be reported (0 to report all) +.TP +.BR libstrongswan.leak_detective.usage_threshold_count " [0]" +Threshold in number of allocations for leaks to be reported (0 to report all) +.TP .BR libstrongswan.processor.priority_threads Subsection to configure the number of reserved threads per priority class see JOB PRIORITY MANAGEMENT @@ -569,7 +817,7 @@ Discard certificates with unsupported or unknown critical extensions .SS libstrongswan.plugins subsection .TP .BR libstrongswan.plugins.attr-sql.database -Database URI for attr-sql plugin used by charon and pluto +Database URI for attr-sql plugin used by charon .TP .BR libstrongswan.plugins.attr-sql.lease_history " [yes]" Enable logging of SQL IP pool leases @@ -580,9 +828,18 @@ Use faster random numbers in gcrypt; for testing only, produces weak keys! .BR libstrongswan.plugins.openssl.engine_id " [pkcs11]" ENGINE ID to use in the OpenSSL plugin .TP +.BR libstrongswan.plugins.openssl.fips_mode " [0]" +Set OpenSSL FIPS mode: disabled(0), enabled(1), Suite B enabled(2) +.TP .BR libstrongswan.plugins.pkcs11.modules List of available PKCS#11 modules .TP +.BR libstrongswan.plugins.pkcs11.load_certs " [yes]" +Whether to load certificates from tokens +.TP +.BR libstrongswan.plugins.pkcs11.reload_certs " [no]" +Reload certificates from all tokens if charon receives a SIGHUP +.TP .BR libstrongswan.plugins.pkcs11.use_dh " [no]" Whether the PKCS#11 modules should be used for DH and ECDH (see use_ecc option) .TP @@ -599,22 +856,63 @@ keys not stored on tokens .TP .BR libstrongswan.plugins.pkcs11.use_rng " [no]" Whether the PKCS#11 modules should be used as RNG +.TP +.BR libstrongswan.plugins.random.random " [@DEV_RANDOM@]" +File to read random bytes from, instead of @DEV_RANDOM@ +.TP +.BR libstrongswan.plugins.random.urandom " [@DEV_URANDOM@]" +File to read pseudo random bytes from, instead of @DEV_URANDOM@ +.TP +.BR libstrongswan.plugins.unbound.resolv_conf " [/etc/resolv.conf]" +File to read DNS resolver configuration from +.TP +.BR libstrongswan.plugins.unbound.trust_anchors " [/etc/ipsec.d/dnssec.keys]" +File to read DNSSEC trust anchors from (usually root zone KSK) +.SS libtls section +.TP +.BR libtls.cipher +List of TLS encryption ciphers +.TP +.BR libtls.key_exchange +List of TLS key exchange methods +.TP +.BR libtls.mac +List of TLS MAC algorithms +.TP +.BR libtls.suites +List of TLS cipher suites .SS libtnccs section .TP .BR libtnccs.tnc_config " [/etc/tnc_config]" TNC IMC/IMV configuration directory .SS libimcv section .TP +.BR libimcv.assessment_result " [yes]" +Whether IMVs send a standard IETF Assessment Result attribute +.TP +.BR libimcv.database +Global IMV policy database URI +.TP .BR libimcv.debug_level " [1]" Debug level for a stand-alone libimcv library .TP +.BR libimcv.load " [random nonce gmp pubkey x509]" +Plugins to load in IMC/IMVs +.TP +.BR libimcv.os_info.name +Manually set the name of the client OS (e.g. Ubuntu) +.TP +.BR libimcv.os_info.version +Manually set the version of the client OS (e.g. 12.04 i686) +.TP +.BR libimcv.policy_script " [ipsec _imv_policy]" +Script called for each TNC connection to generate IMV policies +.TP .BR libimcv.stderr_quiet " [no]" -Disable output to stderr with a stand-alone libimcv library +isable output to stderr with a stand-alone libimcv library +.PP .SS libimcv plugins section .TP -.BR libimcv.plugins.imc-attestation.platform_info -Information on operating system and hardware platform -.TP .BR libimcv.plugins.imc-attestation.aik_blob AIK encrypted private key blob file .TP @@ -633,9 +931,6 @@ Use Quote2 AIK signature instead of Quote signature .BR libimcv.plugins.imv-attestation.cadir Path to directory with AIK cacerts .TP -.BR libimcv.plugins.imv-attestation.database -Path to database with file measurement information -.TP .BR libimcv.plugins.imv-attestation.dh_group " [ecp256]" Preferred Diffie-Hellman group .TP @@ -645,17 +940,20 @@ Preferred measurement hash algorithm .BR libimcv.plugins.imv-attestation.min_nonce_len " [0]" DH minimum nonce length .TP -.BR libimcv.plugins.imv-attestation.platform_info -Information on operating system and hardware platform +.BR libimcv.plugins.imv-attestation.remediation_uri +URI pointing to attestation remediation instructions .TP -.BR libimcv.plugins.imv-scanner.closed_port_policy " [yes]" -By default all ports must be closed (yes) or can be open (no) +.BR libimcv.plugins.imc-os.push_info " [yes]" +Send operating system info without being prompted .TP -.BR libimcv.plugins.imv-scanner.tcp_ports -List of TCP ports that can be open or must be closed +.BR libimcv.plugins.imv-os.remediation_uri +URI pointing to operating system remediation instructions .TP -.BR libimcv.plugins.imv-scanner.udp_ports -List of UDP ports that can be open or must be closed +.BR libimcv.plugins.imc-scanner.push_info " [yes]" +Send open listening ports without being prompted +.TP +.BR libimcv.plugins.imv-scanner.remediation_uri +URI pointing to scanner remediation instructions .TP .BR libimcv.plugins.imc-test.additional_ids " [0]" Number of additional IMC IDs @@ -663,6 +961,12 @@ Number of additional IMC IDs .BR libimcv.plugins.imc-test.command " [none]" Command to be sent to the Test IMV .TP +.BR libimcv.plugins.imc-test.dummy_size " [0]" +Size of dummy attribute to be sent to the Test IMV (0 = disabled) +.TP +.BR libimcv.plugins.imv-test.remediation_uri +URI pointing to test remediation instructions +.TP .BR libimcv.plugins.imc-test.retry " [no]" Do a handshake retry .TP @@ -671,19 +975,6 @@ Command to be sent to the Test IMV in the handshake retry .TP .BR libimcv.plugins.imv-test.rounds " [0]" Number of IMC-IMV retry rounds -.SS libtls section -.TP -.BR libtls.cipher -List of TLS encryption ciphers -.TP -.BR libtls.key_exchange -List of TLS key exchange methods -.TP -.BR libtls.mac -List of TLS MAC algorithms -.TP -.BR libtls.suites -List of TLS cipher suites .SS manager section .TP .BR manager.database @@ -745,38 +1036,14 @@ Session timeout for mediation service .TP .BR openac.load Plugins to load in ipsec openac tool +.SS pacman section +.TP +.BR pacman.database +Database URI for the database that stores the package information .SS pki section .TP .BR pki.load Plugins to load in ipsec pki tool -.SS pluto section -.TP -.BR pluto.dns1 -.TQ -.BR pluto.dns2 -DNS servers assigned to peer via Mode Config -.TP -.BR pluto.load -Plugins to load in IKEv1 pluto daemon -.TP -.BR pluto.nbns1 -.TQ -.BR pluto.nbns2 -WINS servers assigned to peer via Mode Config -.TP -.BR pluto.threads " [4]" -Number of worker threads in pluto -.SS pluto.plugins section -.TP -.BR pluto.plugins.attr -Section to specify arbitrary attributes that are assigned to a peer via -Mode Config -.TP -.BR charon.plugins.kernel-klips.ipsec_dev_count " [4]" -Number of ipsecN devices -.TP -.BR charon.plugins.kernel-klips.ipsec_dev_mtu " [0]" -Set MTU of ipsecN device .SS pool section .TP .BR pool.load @@ -791,7 +1058,7 @@ Plugins to load in ipsec scepclient tool Plugins to load in starter .TP .BR starter.load_warning " [yes]" -Disable charon/pluto plugin load option warning +Disable charon plugin load option warning .SH LOGGER CONFIGURATION The options described below provide a much more flexible way to configure @@ -897,6 +1164,9 @@ Packet encoding/decoding encryption/decryption operations .B tls libtls library messages .TP +.B esp +libipsec library messages +.TP .B lib libstrongwan library messages .TP @@ -1104,7 +1374,7 @@ it within 30 seconds. Under high load, a higher value might be required. .SH LOAD TESTS To do stability testing and performance optimizations, the IKEv2 daemon charon -provides the load-tester plugin. This plugin allows to setup thousands of +provides the load-tester plugin. This plugin allows one to setup thousands of tunnels concurrently against the daemon itself or a remote host. .PP .B WARNING: @@ -1112,6 +1382,20 @@ Never enable the load-testing plugin on productive systems. It provides preconfigured credentials and allows an attacker to authenticate as any user. .SS Options .TP +.BR charon.plugins.load-tester.addrs +Subsection that contains key/value pairs with address pools (in CIDR notation) +to use for a specific network interface e.g. eth0 = 10.10.0.0/16 +.TP +.BR charon.plugins.load-tester.addrs_keep " [no]" +Whether to keep dynamic addresses even after the associated SA got terminated +.TP +.BR charon.plugins.load-tester.addrs_prefix " [16]" +Network prefix length to use when installing dynamic addresses. If set to -1 the +full address is used (i.e. 32 or 128) +.TP +.BR charon.plugins.load-tester.ca_dir +Directory to load (intermediate) CA certificates from +.TP .BR charon.plugins.load-tester.child_rekey " [600]" Seconds to start CHILD_SA rekeying after setup .TP @@ -1121,6 +1405,9 @@ Delay between initiatons for each thread .BR charon.plugins.load-tester.delete_after_established " [no]" Delete an IKE_SA as soon as it has been established .TP +.BR charon.plugins.load-tester.digest " [sha1]" +Digest algorithm used when issuing certificates +.TP .BR charon.plugins.load-tester.dpd_delay " [0]" DPD delay to use in load test .TP @@ -1133,6 +1420,9 @@ EAP secret to use in load test .BR charon.plugins.load-tester.enable " [no]" Enable the load testing plugin .TP +.BR charon.plugins.load-tester.esp " [aes128-sha1]" +CHILD_SA proposal to use for load tests +.TP .BR charon.plugins.load-tester.fake_kernel " [no]" Fake the kernel interface to allow load-testing against self .TP @@ -1142,6 +1432,9 @@ Seconds to start IKE_SA rekeying after setup .BR charon.plugins.load-tester.init_limit " [0]" Global limit of concurrently established SAs during load test .TP +.BR charon.plugins.load-tester.initiator " [0.0.0.0]" +Address to initiate from +.TP .BR charon.plugins.load-tester.initiators " [0]" Number of concurrent initiator threads to use in load test .TP @@ -1151,8 +1444,24 @@ Authentication method(s) the intiator uses .BR charon.plugins.load-tester.initiator_id Initiator ID used in load test .TP +.BR charon.plugins.load-tester.initiator_match +Initiator ID to match against as responder +.TP +.BR charon.plugins.load-tester.initiator_tsi +Traffic selector on initiator side, as proposed by initiator +.TP +.BR charon.plugins.load-tester.initiator_tsr +Traffic selector on responder side, as proposed by initiator +.TP .BR charon.plugins.load-tester.iterations " [1]" -Number of IKE_SAs to initate by each initiator in load test +Number of IKE_SAs to initiate by each initiator in load test +.TP +.BR charon.plugins.load-tester.issuer_cert +Path to the issuer certificate (if not configured a hard-coded value is used) +.TP +.BR charon.plugins.load-tester.issuer_key +Path to private key that is used to issue certificates (if not configured a +hard-coded value is used) .TP .BR charon.plugins.load-tester.pool Provide INTERNAL_IPV4_ADDRs from a named pool @@ -1163,7 +1472,7 @@ Preshared key to use in load test .BR charon.plugins.load-tester.proposal " [aes128-sha1-modp768]" IKE proposal to use in load test .TP -.BR charon.plugins.load-tester.remote " [127.0.0.1]" +.BR charon.plugins.load-tester.responder " [127.0.0.1]" Address to initiation connections to .TP .BR charon.plugins.load-tester.responder_auth " [pubkey]" @@ -1172,11 +1481,25 @@ Authentication method(s) the responder uses .BR charon.plugins.load-tester.responder_id Responder ID used in load test .TP +.BR charon.plugins.load-tester.responder_tsi " [initiator_tsi]" +Traffic selector on initiator side, as narrowed by responder +.TP +.BR charon.plugins.load-tester.responder_tsr " [initiator_tsr]" +Traffic selector on responder side, as narrowed by responder +.TP .BR charon.plugins.load-tester.request_virtual_ip " [no]" Request an INTERNAL_IPV4_ADDR from the server .TP .BR charon.plugins.load-tester.shutdown_when_complete " [no]" Shutdown the daemon after all IKE_SAs have been established +.TP +.BR charon.plugins.load-tester.socket " [unix://${piddir}/charon.ldt]" +Socket provided by the load-tester plugin +.TP +.BR charon.plugins.load-tester.version " [0]" +IKE version to use (0 means use IKEv2 as initiator and accept any version as +responder) +.PP .SS Configuration details For public key authentication, the responder uses the .B \(dqCN=srv, OU=load-test, O=strongSwan\(dq @@ -1211,7 +1534,7 @@ implementation called modpnull. By setting proposal = aes128-sha1-modpnull .EE this wicked fast DH implementation is used. It does not provide any security -at all, but allows to run tests without DH calculation overhead. +at all, but allows one to run tests without DH calculation overhead. .SS Examples .PP In the simplest case, the daemon initiates IKE_SAs against itself using the @@ -1255,9 +1578,9 @@ value if your box can not handle that much load, or decrease it to put more load on it. If the daemon starts retransmitting messages your box probably can not handle all connection attempts. .PP -The plugin also allows to test against a remote host. This might help to test -against a real world configuration. A connection setup to do stress testing of -a gateway might look like this: +The plugin also allows one to test against a remote host. This might help to +test against a real world configuration. A connection setup to do stress +testing of a gateway might look like this: .PP .EX charon { @@ -1332,7 +1655,8 @@ giving up 76s 165s /etc/strongswan.conf .SH SEE ALSO -ipsec.conf(5), ipsec.secrets(5), ipsec(8) +\fBipsec.conf\fR(5), \fBipsec.secrets\fR(5), \fBipsec\fR(8), \fBcharon-cmd\fR(8) + .SH HISTORY Written for the .UR http://www.strongswan.org |