strongSwan

{{title(strongswan.conf Reference)}}

h1. strongswan.conf

bq. *Please note:* This page documents the configuration options of the most current release. Therefore, you should always consult the strongswan.conf(5) man page that comes with the release you are using to confirm which options are actually available.

h2. Overview

While the [[IpsecConf|ipsec.conf]] configuration file is well suited to define IPsec related configuration parameters, it is not useful for other strongSwan applications to read options from this file. The file is hard to parse and only [[IpsecStarter|ipsec starter]] is capable of doing so. As the number of components of the strongSwan project is continually growing, we needed a more flexible configuration file that is easy to extend and can be used by all components. The new configuration format consists of hierarchical sections and a list of key/value pairs in each section. Starting with the strongSwan 4.2.1 release, a default strongswan.conf file is installed in your sysconfdir, e.g. _/etc/strongswan.conf_.

h2. Syntax

Each section has a name, followed by C-Style curly brackets defining the sections body. Each section body contains a set of subsections and key/value pairs:

<pre>

settings := (section|keyvalue)*

section  := name { settings }

keyvalue := key = value\n

</pre>

Values must be terminated by a newline. Comments are possible using the #-character, but be careful: The parser implementation is currently limited and does not like braces in comments. Section names and keys may contain any printable character except:

<pre>

. { } # \n \t space

</pre>

An example might look like this:

<pre>

a = b

section-one {

  somevalue = asdf

  subsection {

    othervalue = xxx

  }

  # yei, a comment 

  yetanother = zz

}

section-two {

  x = 12

}

</pre>

Indentation is optional, you may use tabs or spaces.

h2. Including files

[[451|Version 4.5.1]] introduced the *include* statement which allows to include other files into strongswan.conf, e.g.

<pre>

include /some/path/*.conf

</pre>

If the file name is not an absolute path, it is considered to be relative to the directory of the file containing the

include statement. The file name may include shell wildcards. Also, such inclusions can be nested.

Sections loaded from the included files *extend* previously loaded sections; already existing values are *replaced*.

It is important to note that settings are added relative to the section the include statement is in.

As an example, the following three files result in the same final config as the one given above:

<pre>

a = b

section-one {

    somevalue = before include

    include include.conf

}

include other.conf

</pre>

include.conf:

<pre>

# settings loaded from this file are added to section-one

# the following replaces the previous value

somevalue = asdf

subsection {

    othervalue = yyy

}

yetanother = zz

</pre>

other.conf:

<pre>

# this extends section-one and subsection

section-one {

    subsection {

        # this replaces the previous value

        othervalue = xxx

    }

}

section-two {

    x = 12

}

</pre>

h2. Reading values

The config file is read by libstrongswan during library initialization. Values are accessed using a dot-separated section list and a key: 

Accessing *section-one.subsection.othervalue* will return *xxx*.

Have a look at the settings interface (source:src/libstrongswan/settings.h) to learn about the details.

h2. Defined keys

The following keys are currently defined (using dot notation).

*${piddir}* refers to the directory that can be [[AutoConf|configured]] with the _--with-piddir_ option (defaults to _/var/run_).

|_<.Key                                             |_<.Default|_<.Description|

|\3(level1). *attest section*                       |

|attest.database                                    |          |File  measurement  information  database  URI.  If it contains a password, make sure to adjust the permissions of the config file accordingly.|

|attest.load                                        |          |Plugins to load in ipsec attest tool.|

|\3(level1). *charon section*                       |

|\3(level2). *Note:* Many of the options in this section also apply to [[charon-cmd]] and other _charon_ derivatives. Just use their respective name (e.g. _charon-cmd_ instead of _charon_).|

|\3(level3). Defaults for options in this section can be configured in the _libstrongswan_ section.|

|charon.block_threshold                             |5         |Maximum number of half-open IKE_SAs for a single peer IP.|

|charon.cert_cache                                  |yes       |Whether relations in validated certificate chains should be cached in memory.|

|charon.cisco_unity                                 |no        |Send Cisco Unity vendor ID payload (IKEv1 only), see [[UnityPlugin|unity plugin]].|

|charon.close_ike_on_child_failure                  |no        |Close the IKE_SA if setup of the CHILD_SA along with IKE_AUTH failed.|

|charon.cookie_threshold                            |10        |Number of half-open IKE_SAs that activate the cookie mechanism.|

|charon.crypto_test.bench                           |no        |Benchmark crypto algorithms and order them by efficiency.|

|charon.crypto_test.bench_size                      |1024      |Buffer size used for crypto benchmark.|

|charon.crypto_test.bench_time                      |50        |Number of iterations to test each algorithm.|

|charon.crypto_test.on_add                          |no        |Test crypto algorithms during registration (requires test vectors provided by the _test-vectors_ plugin).|

|charon.crypto_test.on_create                       |no        |Test crypto algorithms on each crypto primitive instantiation.|

|charon.crypto_test.required                        |no        |Strictly require at least one test vector to enable an algorithm.|

|charon.crypto_test.rng_true                        |no        |Whether to test RNG with TRUE quality; requires a lot of entropy.|

|charon.dh_exponent_ansi_x9_42                      |yes       |Use ANSI X9.42 DH exponent size or optimum size matched to cryptographical strength.|

|charon.dns1                                        |          |DNS server assigned to peer via configuration payload (CP), see [[AttrPlugin|attr plugin]].|

|charon.dns2                                        |          |DNS server assigned to peer via configuration payload (CP).|

|charon.dos_protection                              |yes       |Enable Denial of Service protection using cookies and aggressiveness checks.|

|charon.ecp_x_coordinate_only                       |yes       |Compliance with the errata for RFC 4753.|

|charon.filelog                                     |          |Section to define file loggers, see [[LoggerConfiguration]].|

|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.|

|charon.fragment_size                               |512       |Maximum size (in bytes) of a sent fragment when using the proprietary IKEv1 fragmentation extension.|

|charon.group                                       |          |Name of the [[ReducedPrivileges|group]] the daemon changes to after startup.|

|charon.half_open_timeout                           |30        |Timeout in seconds for connecting IKE_SAs, also see [[JobPriority#IKE_SA_INIT-dropping|IKE_SA_INIT dropping]].|

|charon.hash_and_url                                |no        |Enable hash and URL support.|

|charon.host_resolver.max_threads                   |3         |Maximum number of concurrent resolver threads (they are terminated if unused).|

|charon.host_resolver.min_threads                   |0         |Minimum number of resolver threads to keep around.|

|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).|

|charon.ignore_routing_tables                       |          |A space-separated list of routing tables to be excluded from route lookup.|

|charon.ikesa_limit                                 |0         |Maximum number of IKE_SAs that can be established at the same time before new connection attempts are blocked.|

|charon.ikesa_table_segments                        |1         |Number of exclusively locked segments in the hash table, see [[IkeSaTable|IKE_SA lookup tuning]].|

|charon.ikesa_table_size                            |1         |Size of the IKE_SA hash table, see [[IkeSaTable|IKE_SA lookup tuning]].|

|charon.inactivity_close_ike                        |no        |Whether to close IKE_SA if the only CHILD_SA closed due to inactivity.|

|charon.init_limit_half_open                        |0         |Limit new connections based on the current number of half open IKE_SAs, see [[JobPriority#IKE_SA_INIT-dropping|IKE_SA_INIT dropping]].|

|charon.init_limit_job_load                         |0         |Limit new connections based on the number of jobs currently queued for processing, see [[JobPriority#IKE_SA_INIT-dropping|IKE_SA_INIT dropping]].|

|charon.initiator_only                              |no        |Causes charon daemon to ignore IKE initiation requests.|

|charon.install_routes                              |yes       |Install routes into a separate routing table for established IPsec tunnels.|

|charon.install_virtual_ip                          |yes       |Install virtual IP addresses.|

|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.|

|charon.integrity_test                              |no        |Check daemon, libstrongswan and plugin integrity at startup.|

|charon.interfaces_ignore                           |          |A comma-separated list of network interfaces that should be ignored, if _charon.interfaces_use_ is specified this option has no effect.|

|charon.interfaces_use                              |          |A comma-separated list of network interfaces that should be used by charon. All other interfaces are ignored.|

|charon.keep_alive                                  |20s       |NAT keep alive interval.|

|charon.leak_detective.detailed                     |yes       |Includes source file names and line numbers in leak detective output.|

|charon.leak_detective.usage_threshold              |10240     |Threshold in bytes for leaks to be reported (0 to report all).|

|charon.leak_detective.usage_threshold_count        |0         |Threshold in number of allocations for leaks to be reported (0 to report all).|

|charon.load                                        |          |Plugins to load in IKEv2 charon daemon, see [[PluginLoad]].|

|charon.load_modular                                |no        |If enabled the list of plugins to load is determined by individual _load_ settings for each plugin, see [[PluginLoad#Modular-Configuration]].|

|charon.max_packet                                  |10000     |Maximum packet size accepted by charon.|

|charon.multiple_authentication                     |yes       |Enable multiple authentication exchanges (RFC 4739).|

|charon.nbns1                                       |          |WINS server assigned to peer via configuration payload (CP), see [[AttrPlugin|attr plugin]].|

|charon.nbns2                                       |          |WINS server assigned to peer via configuration payload (CP).|

|charon.port                                        |500       |UDP port used locally. If set to 0 a random port will be allocated.|

|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 _charon.port_, otherwise a random port will be allocated.|

|charon.process_route                               |yes       |Process RTM_NEWROUTE and RTM_DELROUTE events.|

|charon.processor.priority_threads                  |          |Subsection to configure the number of reserved threads per priority class (see [[JobPriority]]).|

|charon.receive_delay                               |0         |Delay in ms for receiving packets, to simulate larger RTT.|

|charon.receive_delay_response                      |yes       |Delay response messages.|

|charon.receive_delay_request                       |yes       |Delay request messages.|

|charon.receive_delay_type                          |0         |Specific IKEv2 message type to delay, 0 for any.|

|charon.replay_window                               |32        |Size of the AH/ESP replay window, in packets.|

|charon.retransmit_base                             |1.8       |Base to use for calculating exponential back off, see [[Retransmission]].|

|charon.retransmit_timeout                          |4.0       |Timeout in seconds before sending first retransmit.|

|charon.retransmit_tries                            |5         |Number of times to retransmit a packet before giving up.|

|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.|

|charon.reuse_ikesa                                 |yes       |Initiate CHILD_SA within existing IKE_SAs.|

|charon.routing_table                               |          |Numerical routing table to install routes to.|

|charon.routing_table_prio                          |          |Priority of the routing table.|

|charon.send_delay                                  |0         |Delay in ms for sending packets, to simulate larger RTT.|

|charon.send_delay_request                          |yes       |Delay request messages.|

|charon.send_delay_response                         |yes       |Delay response messages.|

|charon.send_delay_type                             |0         |Specific IKEv2 message type to delay, 0 for any.|

|charon.send_vendor_id                              |no        |Send strongSwan vendor ID payload.|

|charon.syslog                                      |          |Section to define syslog loggers, see [[LoggerConfiguration]].|

|charon.threads                                     |16        |Number of worker threads in charon. Several of these are reserved for long running tasks in internal modules and plugins. Therefore, make sure you don't set this value too low. The number of idle worker threads listed in _[[IPsecCommand|ipsec]] statusall_ might be used as indicator on the number of reserved threads ([[JobPriority]] has more on this).|

|charon.user                                        |          |Name of the [[ReducedPrivileges|user]] the daemon changes to after startup.|

|charon.x509.enforce_critical                       |yes       |Discard certificates with unsupported or unknown critical extensions.|

|\3(level2). *charon.plugins subsection*            |

|charon.plugins.android_log.loglevel                |1         |Loglevel for logging to Android specific logger.|

|charon.plugins.attr                                |          |Section to specify arbitrary attributes that are assigned to a peer via configuration payload, see [[AttrPlugin|attr plugin]].|

|charon.plugins.attr-sql.database                   |          |Database  URI for [[attrsql|attr-sql plugin]] used by charon. If it contains a password, make sure to adjust the permissions  of  the  config file accordingly.|

|charon.plugins.attr-sql.lease_history              |yes       |Enable logging of [[SQL]] IP pool leases.|

|charon.plugins.certexpire.csv.cron                 |          |Cron style string specifying CSV export times, see [[certexpire]] for details.|

|charon.plugins.certexpire.csv.empty_string         |          |String to use in empty intermediate CA fields.|

|charon.plugins.certexpire.csv.fixed_fields         |yes       |Use a fixed intermediate CA field count.|

|charon.plugins.certexpire.csv.force                |yes       |Force export of all trustchains we have a private key for.|

|charon.plugins.certexpire.csv.format               |%d:%m:%Y  |strftime(3) format string to export expiration dates as.|

|charon.plugins.certexpire.csv.local                |          |strftime(3) format string for the CSV file name to export local certificates to.|

|charon.plugins.certexpire.csv.remote               |          |strftime(3) format string for the CSV file name to export remote certificates to.|

|charon.plugins.certexpire.csv.separator            |,         |CSV field separator.|

|charon.plugins.coupling.file                       |          |File to store coupling list to, see [[CertCoupling|certcoupling plugin]] for details.|

|charon.plugins.coupling.hash                       |sha1      |Hashing algorithm to fingerprint coupled certificates.|

|charon.plugins.coupling.max                        |1         |Maximum number of coupling entries to create.|

|charon.plugins.dhcp.force_server_address           |no        |Always use the configured server address, see [[DHCPPlugin|DHCP plugin]] for details.|

|charon.plugins.dhcp.identity_lease                 |no        |Derive user-defined MAC address from hash of IKEv2 identity.|

|charon.plugins.dhcp.interface                      |          |Interface name the plugin uses for address allocation. The default is to bind to any and let the system decide which way to route the packets to the DHCP server.|

|charon.plugins.dhcp.server                         |255.255.255.255|DHCP server unicast or broadcast IP address.|

|charon.plugins.dnscert.enable                      |no        |Enable fetching of CERT RRs via DNS.|

|charon.plugins.duplicheck.enable                   |yes       |Enable [[duplicheck]] plugin (if loaded).|

|charon.plugins.duplicheck.socket                   |unix://${piddir}/charon.dck|Socket provided by the [[duplicheck]] plugin.|

|charon.plugins.eap-aka.request_identity            |yes       ||

|charon.plugins.eap-aka-3ggp2.seq_check             |          ||

|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.|

|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.|

|charon.plugins.eap-gtc.backend                     |pam       |XAuth backend to be used for credential verification, see [[EapGtc|EAP-GTC]].|

|charon.plugins.eap-peap.fragment_size              |1024      |Maximum size of an EAP-PEAP packet.|

|charon.plugins.eap-peap.max_message_count          |32        |Maximum number of processed EAP-PEAP packets.|

|charon.plugins.eap-peap.include_length             |no        |Include length in non-fragmented EAP-PEAP packets.|

|charon.plugins.eap-peap.phase2_method              |mschapv2  |Phase2 EAP client authentication method.|

|charon.plugins.eap-peap.phase2_piggyback           |no        |Phase2 EAP Identity request piggybacked by server onto TLS Finished message.|

|charon.plugins.eap-peap.phase2_tnc                 |no        |Start phase2 EAP-TNC protocol after successful client authentication.|

|charon.plugins.eap-peap.request_peer_auth          |no        |Request peer authentication based on a client certificate.|

|charon.plugins.eap-radius.accounting               |no        |Enable EAP-RADIUS accounting.|

|charon.plugins.eap-radius.accounting_requires_vip  |no        |If enabled, accounting is disabled unless an IKE_SA has at least one virtual IP.|

|charon.plugins.eap-radius.class_group              |no        |Use the class attribute sent in the RADIUS-Accept message as group membership information, see [[EapRadius]].|

|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.|

|charon.plugins.eap-radius.dae.enable               |no        |Enables support for the Dynamic Authorization Extension (RFC 5176).|

|charon.plugins.eap-radius.dae.listen               |0.0.0.0   |Address to listen for DAE messages from the RADIUS server.|

|charon.plugins.eap-radius.dae.port                 |3799      |Port to listen for DAE requests.|

|charon.plugins.eap-radius.dae.secret               |          |Shared secret used to verify/sign DAE messages.If  set, make sure to adjust the permissions of the config file accordingly.|

|charon.plugins.eap-radius.eap_start                |no        |Send EAP-Start instead of EAP-Identity to start RADIUS conversation.|

|charon.plugins.eap-radius.filter_id                |no        |Use the filter_id attribute sent in the RADIUS-Accept message as group membership if the RADIUS tunnel_type attribute is set to ESP.|

|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).|

|charon.plugins.eap-radius.forward.radius_to_ike    |          |Same as above but from RADIUS to IKEv2, a strongSwan specific private notify (40969) is used to transmit the attributes.|

|charon.plugins.eap-radius.id_prefix                |          |Prefix to EAP-Identity, some AAA servers use a IMSI prefix to select the EAP method.|

|charon.plugins.eap-radius.nas_identifier           |strongSwan|NAS-Identifier to include in RADIUS messages.|

|charon.plugins.eap-radius.port                     |1812      |Port of RADIUS server (authentication).|

|charon.plugins.eap-radius.secret                   |          |Shared secret between RADIUS and NAS. If set, make sure to adjust the permissions of the config file accordingly.|

|charon.plugins.eap-radius.server                   |          |IP/Hostname of RADIUS server.|

|charon.plugins.eap-radius.servers                  |          |Section to specify multiple RADIUS servers, see [[EapRadius]]. The _nas_identifier_, _secret_, _sockets_ and _port_ (or _auth_port_) options can be specified for each server. A server's IP/Hostname can be configured using the _address_ option. The _acct_port_ [1813] option can be used to specify the port used for RADIUS accounting. For each server a priority can be specified using the _preference_ [0] option.|

|charon.plugins.eap-radius.sockets                  |1         |Number of sockets (ports) to use, increase for high load.|

|charon.plugins.eap-radius.xauth                    |          |Section to configure [[EapRadius#XAuth|multiple XAuth authentication rounds]] via RADIUS.|

|charon.plugins.eap-sim.request_identity            |yes       ||

|charon.plugins.eap-simaka-sql.database             |          ||

|charon.plugins.eap-simaka-sql.remove_used          |          ||

|charon.plugins.eap-tls.fragment_size               |1024      |Maximum size of an EAP-TLS packet.|

|charon.plugins.eap-tls.include_length              |yes       |Include length in non-fragmented EAP-TLS packets.|

|charon.plugins.eap-tls.max_message_count           |32        |Maximum number of processed EAP-TLS packets (0 = no limit).|

|charon.plugins.eap-tnc.max_message_count           |10        |Maximum number of processed EAP-TNC packets (0 = no limit).|

|charon.plugins.eap-tnc.protocol                    |tnccs-1.1 |IF-TNCCS protocol version to be used (tnccs-1.1, tnccs-2.0, tnccs-dynamic).|

|charon.plugins.eap-ttls.fragment_size              |1024      |Maximum size of an EAP-TTLS packet.|

|charon.plugins.eap-ttls.include_length             |yes       |Include length in non-fragmented EAP-TTLS packets.|

|charon.plugins.eap-ttls.max_message_count          |32        |Maximum number of processed EAP-TTLS packets (0 = no limit).|

|charon.plugins.eap-ttls.phase2_method              |md5       |Phase2 EAP client authentication method.|

|charon.plugins.eap-ttls.phase2_piggyback           |no        |Phase2 EAP Identity request piggybacked by server onto TLS Finished message.|

|charon.plugins.eap-ttls.phase2_tnc                 |no        |Start phase2 EAP TNC protocol after successful client authentication.|

|charon.plugins.eap-ttls.request_peer_auth          |no        |Request peer authentication based on a client certificate.|

|charon.plugins.error-notify.socket                 |unix://${piddir}/charon.enfy|Socket provided by the [[ErrorNotifyPlugin|error-notify]] plugin.|

|charon.plugins.gcrypt.quick_random                 |no        |Use faster random numbers in gcrypt. *For testing only, produces weak keys!*|

|charon.plugins.ha.autobalance                      |0         |Interval in seconds to automatically balance handled segments between nodes. Set to 0 to disable.|

|charon.plugins.ha.fifo_interface                   |yes       ||

|charon.plugins.ha.heartbeat_delay                  |1000      ||

|charon.plugins.ha.heartbeat_timeout                |2100      ||

|charon.plugins.ha.local                            |          ||

|charon.plugins.ha.monitor                          |yes       ||

|charon.plugins.ha.pools                            |          ||

|charon.plugins.ha.remote                           |          ||

|charon.plugins.ha.resync                           |yes       ||

|charon.plugins.ha.secret                           |          ||

|charon.plugins.ha.segment_count                    |1         ||

|charon.plugins.imc-attestation.aik_blob            |          |AIK encrypted private key blob file.|

|charon.plugins.imc-attestation.aik_cert            |          |AIK certificate file.|

|charon.plugins.imc-attestation.aik_key             |          |AIK public key file.|

|charon.plugins.imc-attestation.nonce_len           |20        |DH nonce length.|

|charon.plugins.imc-attestation.pcr_info            |yes       |Whether to send pcr_before and pcr_after info.|

|charon.plugins.imc-attestation.use_quote2          |yes       |Use Quote2 AIK signature instead of Quote signature.|

|charon.plugins.imc-os.push_info                    |yes       |Send operating system info without being prompted.|

|charon.plugins.imc-scanner.push_info               |yes       |Send open listening ports without being prompted.|

|charon.plugins.imc-swid.swid_directory             |${prefix}/share|Directory where SWID tags are located.|

|charon.plugins.imc-test.additional_ids             |0         |Number of additional IMC IDs.|

|charon.plugins.imc-test.command                    |none      |Command to be sent to the Test IMV.|

|charon.plugins.imc-test.dummy_size                 |0         |Size of dummy attribute to be sent to the Test IMV (0 = disabled).|

|charon.plugins.imc-test.retry                      |no        |Do a handshake retry.|

|charon.plugins.imc-test.retry_command              |          |Command to be sent to the IMV Test in the handshake retry.|

|charon.plugins.imv-attestation.cadir               |          |Path to directory with AIK cacerts.|

|charon.plugins.imv-attestation.dh_group            |ecp256    |Preferred Diffie-Hellman group.|

|charon.plugins.imv-attestation.hash_algorithm      |sha256    |Preferred measurement hash algorithm.|

|charon.plugins.imv-attestation.min_nonce_len       |0         |DH minimum nonce length.|

|charon.plugins.imv-attestation.remediation_uri     |          |URI pointing to attestation remediation instructions.|

|charon.plugins.imv-os.remediation_uri              |          |URI pointing to operating system remediation instructions.|

|charon.plugins.imv-scanner.remediation_uri         |          |URI pointing to scanner remediation instructions.|

|charon.plugins.imv-test.rounds                     |0         |Number of IMC-IMV retry rounds.|

|charon.plugins.ipseckey.enable                     |no        |Enable fetching of IPSECKEY RRs via DNS.|

|charon.plugins.kernel-klips.ipsec_dev_count        |4         |Number of ipsecN devices.|

|charon.plugins.kernel-klips.ipsec_dev_mtu          |0         |Set MTU of ipsecN device.|

|charon.plugins.kernel-libipsec.allow_peer_ts       |no        |Allow that the remote traffic selector equals the IKE peer (see [[kernel-libipsec#Host-to-Host-Tunnels|kernel-libipsec]] for details).|

|charon.plugins.kernel-netlink.xfrm_acq_expires     |165       |Lifetime of XFRM acquire state in kernel. The value gets written to @/proc/sys/net/core/xfrm_acq_expires@. Indirectly controls the dealy of XFRM acquire messages sent.|

|charon.plugins.kernel-netlink.fwmark               |          |Firewall mark to set on the routing rule that directs traffic to our own routing table. The format is [!]mark[/mask], where the optional exclamation mark inverts the meaning (i.e. the rule only applies to packets that don't match the mark). A possible use case are [[kernel-libipsec#Host-to-Host-Tunnels|host-to-host tunnels with kernel-libipsec]].|

|charon.plugins.kernel-netlink.roam_events          |yes       |Whether to trigger roam events when interfaces, addresses or routes change.|

|charon.plugins.kernel-pfroute.vip_wait             |1000      |Time in ms to wait until virtual IP addresses appear/disappear before failing.|

|charon.plugins.led.activity_led                    |          ||

|charon.plugins.led.blink_time                      |50        ||

|charon.plugins.load-tester                         |          |Subsection to configure [[LoadTests|load tests]] using the [[LoadTests|load-tester]] plugin.|

|charon.plugins.lookip.socket                       |unix://${piddir}/charon.lkp|Socket provided by the [[lookip]] plugin.|

|charon.plugins.ntru.max_drbg_requests              |4294967294|Number of pseudo-random bit requests from the DRBG before an automatic reseeding occurs.|

|charon.plugins.ntru.parameter_set                  |optimum   |The following parameter sets are available: x9_98_speed, x9_98_bandwidth, x9_98_balance and optimum, the last set not being part of the X9.98 standard but  having  the best performance.|

|charon.plugins.openssl.engine_id                   |pkcs11    |ENGINE ID to use in the OpenSSL plugin.|

|charon.plugins.openssl.fips_mode                   |0         |Set OpenSSL FIPS mode: disabled (0), enabled (1), Suite B enabled (2). Defaults to the value [[Autoconf#--with-options|configured]] with the _--with-fips-mode_ option.|

|charon.plugins.pkcs11.load_certs                   |yes       |Whether to load certificates from tokens.|

|charon.plugins.pkcs11.modules                      |          |List of available PKCS#11 modules, see [[SmartCardsIKEv2]].|

|charon.plugins.pkcs11.reload_certs                 |no        |Reload certificates from all tokens if charon receives a SIGHUP.|

|charon.plugins.pkcs11.use_dh                       |no        |Whether the PKCS#11 modules should be used for DH and ECDH.|

|charon.plugins.pkcs11.use_ecc                      |no        |Whether the PKCS#11 modules should be used for ECDH and ECDSA public key operations. ECDSA private keys are used regardless of this option.|

|charon.plugins.pkcs11.use_hasher                   |no        |Whether the PKCS#11 modules should be used to hash data.|

|charon.plugins.pkcs11.use_pubkey                   |no        |Whether the PKCS#11 modules should be used for public key operations, even for keys not stored on tokens.|

|charon.plugins.pkcs11.use_rng                      |no        |Whether the PKCS#11 modules should be used as RNG.|

|charon.plugins.radattr.dir                         |          |Directory where RADIUS attributes are stored in client-ID specific files, see [[RadAttrPlugin|radattr]].|

|charon.plugins.radattr.message_id                  |-1        |RADIUS attributes are added to all IKE_AUTH messages by default (-1), or only to the IKE_AUTH message with the given IKEv2 message ID.|

|charon.plugins.random.random                       |/dev/random|File to read random bytes from.|

|charon.plugins.random.urandom                      |/dev/urandom|File to read pseudo random bytes from.|

|charon.plugins.random.strong_equals_true           |no        |If enabled the RNG_STRONG class reads random bytes from the same source as the RNG_TRUE class.|

|charon.plugins.resolve.file                        |/etc/resolv.conf|File used by the [[resolveplugin|resolve plugin]] to write DNS server entries to.|

|charon.plugins.resolve.resolvconf.iface_prefix     |lo.inet.ipsec.|Prefix used by the [[resolveplugin|resolve plugin]] for interface names sent to resolvconf(8). The name server address 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).|

|charon.plugins.socket-default.fwmark               |          |Firewall mark to set on outbound packets (a possible use case are [[kernel-libipsec#Host-to-Host-Tunnels|host-to-host tunnels with kernel-libipsec]]).|

|charon.plugins.socket-default.set_source           |yes       |Set source address on outbound packets, if possible.|

|charon.plugins.socket-default.use_ipv4             |yes       |Listen on IPv4, if possible.|

|charon.plugins.socket-default.use_ipv6             |yes       |Listen on IPv6, if possible.|

|charon.plugins.sql.database                        |          |Database URI for charon's [[SQL]] plugin. If it contains a password, make sure to adjust the permissions of the config  file  accordingly.|

|charon.plugins.sql.loglevel                        |-1        |Loglevel for logging to [[SQL]] database.|

|charon.plugins.stroke.ignore_missing_ca_basic_constraint|no   |Treat certificates in [[IpsecDirectoryCacerts|ipsec.d/cacerts]] and ipsec.conf [[CASection|ca sections]] as CA certificates even if they don't contain a CA basic constraint.|

|charon.plugins.stroke.max_concurrent               |4         |Maximum number of stroke messages handled concurrently.|

|charon.plugins.stroke.socket                       |unix://${piddir}/charon.ctl|Socket provided by the stroke plugin.|

|charon.plugins.stroke.timeout                      |0         |Timeout in ms for any stroke command. Use 0 to disable the timeout.|

|charon.plugins.systime-fix.interval                |0         |Interval in seconds to check system time for validity. 0 disables the check. See [[SystimeFixPlugin|systime-fix plugin]].|

|charon.plugins.systime-fix.reauth                  |no        |Whether to use reauth or delete if an invalid cert lifetime is detected.|

|charon.plugins.systime-fix.threshold               |          |Threshold date where system time is considered valid. Disabled if not specified.|

|charon.plugins.systime-fix.threshold_format        |%Y        |strptime(3) format used to parse threshold option.|

|charon.plugins.tnc-ifmap.client_cert               |          |Path to X.509 certificate file of IF-MAP client.|

|charon.plugins.tnc-ifmap.client_key                |          |Path to private key file of IF-MAP client.|

|charon.plugins.tnc-ifmap.device_name               |          |Unique name of strongSwan server as a PEP and/or PDP device.|

|charon.plugins.tnc-ifmap.renew_session_interval    |150       |Interval in seconds between periodic IF-MAP RenewSession requests.|

|charon.plugins.tnc-ifmap.server_cert               |          |Path to X.509 certificate file of IF-MAP server.|

|charon.plugins.tnc-ifmap.server_uri                |https://localhost:8444/imap|URI of the form <notextile>[https://]servername[:port][/path]</notextile>.|

|charon.plugins.tnc-ifmap.username_password         |          |Credentials of IF-MAP client of the form username:password. If set,  make  sure  to adjust  the permissions of the config file accordingly.|

|charon.plugins.tnc-imc.dlcose                      |yes       |Unload IMC after use.|

|charon.plugins.tnc-imc.preferred_language          |en        |Preferred language for TNC recommendations.|

|charon.plugins.tnc-imv.dlcose                      |yes       |Unload IMV after use.|

|charon.plugins.tnc-imv.recommendation_policy       |default   |TNC recommendation policy, one of _default_, _any_, or _all_.|

|charon.plugins.tnc-pdp.pt_tls.enable               |yes       |Enable PT-TLS protocol on the strongSwan PDP.|

|charon.plugins.tnc-pdp.pt_tls.port                 |271       |PT-TLS server port the strongSwan PDP is listening on.|

|charon.plugins.tnc-pdp.radius.enable               |yes       |Enable RADIUS protocol on the strongSwan PDP.|

|charon.plugins.tnc-pdp.radius.method               |ttls      |EAP tunnel method to be used.|

|charon.plugins.tnc-pdp.radius.port                 |1812      |RADIUS server port the strongSwan PDP is listening on.|

|charon.plugins.tnc-pdp.radius.secret               |          |Shared RADIUS secret between strongSwan PDP and NAS. If set, make  sure  to adjust the permissions of the config file accordingly.|

|charon.plugins.tnc-pdp.server                      |          |Name of the strongSwan PDP as contained in the AAA certificate.|

|charon.plugins.tnc-pdp.timeout                     |          |Timeout in seconds before closing incomplete connections.|

|charon.plugins.tnccs-11.max_message_size           |45000     |Maximum size of a PA-TNC message (XML & Base64 encoding).|

|charon.plugins.tnccs-20.max_batch_size             |65522     |Maximum size of a PB-TNC batch (upper limit via PT-EAP = 65529).|

|charon.plugins.tnccs-20.max_message_size           |65490     |Maximum size of a PA-TNC message (upper limit via PT-EAP = 65497).|

|charon.plugins.unbound.dlv_anchors                 |          |File to read trusted keys for DLV(DNSSEC Lookaside Validation) from. It uses the same format as _trust_anchors_. Only one DLV can be configured, which is then used as a root trusted DLV, this means that it is a lookaside for the root.|

|charon.plugins.unbound.resolv_conf                 |/etc/resolv.conf|File to read DNS resolver configuration from.|

|charon.plugins.unbound.trust_anchors               |/etc/ipsec.d/dnssec.keys|File to read DNSSEC trust anchors from (usually root zone KSK). The format of the file is the standard DNS Zone file format, anchors can be stored as DS or DNSKEY entries in the file.|

|charon.plugins.updown.dns_handler                  |no        |Whether the updown script should handle DNS servers assigned via IKEv1 Mode Config or IKEv2 Config Payloads (if enabled they can't be handled by other plugins, like [[resolveplugin|resolve]]).|

|charon.plugins.whitelist.enable                    |yes       |Enable loaded [[whitelist]] plugin.|

|charon.plugins.whitelist.socket                    |unix://${piddir}/charon.wlst|Socket provided by the whitelist plugin.|

|charon.plugins.xauth-eap.backend                   |radius    |EAP plugin to be used as backend for XAuth credential verification, see [[XAuthEAP]].|

|charon.plugins.xauth-pam.pam_service               |login     |PAM service to be used for authentication, see [[XAuthPAM]].|

|charon.plugins.xauth-pam.session                   |no        |Open/close a PAM session for each active IKE_SA.|

|charon.plugins.xauth-pam.trim_email                |yes       |If an email address is given as an XAuth username, trim it to just the username part.|

|\3(level2). *charon.imcv subsection*               |

|\3(level3). Defaults for options in this section can be configured in the _libimcv_ section.|

|charon.imcv.assessment_result                      |yes       |Whether IMVs send a standard IETF Assessment Result attribute.|

|charon.imcv.database                               |          |Global IMV policy database URI. If it contains a password, make sure to adjust the permissions of the config file accordingly.|

|charon.imcv.os_info.name                           |          |Manually set the name of the client OS (e.g. Ubuntu).|

|charon.imcv.os_info.version                        |          |Manually set the version of the client OS (e.g. 12.04 i686).|

|charon.imcv.policy_script                          |ipsec _imv_policy|Script called for each TNC connection to generate IMV policies.|

|\3(level2). *charon.tls subsection*                |

|\3(level3). Defaults for options in this section can be configured in the _libtls_ section.|

|charon.tls.cipher                                  |          |List of TLS encryption ciphers.|

|charon.tls.key_exchange                            |          |List of TLS key exchange methods.|

|charon.tls.mac                                     |          |List of TLS MAC algorithms.|

|charon.tls.suites                                  |          |List of TLS cipher suites.|

|\3(level2). *charon.tnc subsection*                |

|\3(level3). Defaults for options in this section can be configured in the _libtnccs_ section.|

|libtnccs.tnc_config                                |/etc/tnc_config|TNC IMC/IMV configuration file.|

|\3(level1). *libimcv section*                      |

|libimcv.debug_level                                |1         |Debug level for a stand-alone libimcv library.|

|libimcv.load                                       |random nonce gmp pubkey x509|Plugins to load in IMC/IMVs with stand-alone libimcv library.|

|libimcv.stderr_quiet                               |no        |Disable the output to stderr with a stand-alone libimcv library.|

|\3(level1). *manager section*                      |

|manager.database                                   |          |Credential database URI for manager. If it contains a password, make sure to adjust the permissions of the config file accordingly.|

|manager.debug                                      |no        |Enable debugging in manager.|

|manager.load                                       |          |Plugins to load in manager.|

|manager.socket                                     |          |FastCGI socket of manager, to run it statically.|

|manager.threads                                    |10        |Threads to use for request handling.|

|manager.timeout                                    |15m       |Session timeout for manager.|

|\3(level1). *mediation client section*             |

|medcli.database                                    |          |Mediation client database URI. If it contains a password, make sure to adjust the permissions of the config file accordingly.|

|medcli.dpd                                         |5m        |DPD timeout to use in mediation client plugin.|

|medcli.rekey                                       |20m       |Rekeying time on mediation connections in mediation client plugin.|

|\3(level1). *mediation server section*             |

|medsrv.database                                    |          |Mediation server database URI. If it contains a  password, make sure to adjust the permissions of the config file accordingly.|

|medsrv.debug                                       |no        |Debugging in mediation server web application.|

|medsrv.dpd                                         |5m        |DPD timeout to use in mediation server plugin.|

|medsrv.load                                        |          |Plugins to load in mediation server plugin.|

|medsrv.password_length                             |6         |Minimum password length required for mediation server user accounts.|

|medsrv.rekey                                       |20m       |Rekeying time on mediation connections in mediation server plugin.|

|medsrv.socket                                      |          |Run Mediation server web application statically on socket.|

|medsrv.threads                                     |5         |Number of thread for mediation service web application.|

|medsrv.timeout                                     |15m       |Session timeout for mediation service.|

|\3(level1). *openac section*                       |

|openac.load                                        |          |Plugins to load in ipsec openac tool.|

|\3(level1). *pacman section*                       |

|pacman.database                                    |          |Database  URI for the database that stores the package information. If it contains a password, make sure to adjust the permissions of the config file accordingly.|

|\3(level1). *pki section*                          |

|pki.load                                           |          |Plugins to load in ipsec pki tool.|

|\3(level1). *pool section*                         |

|pool.database                                      |          |Database  URI for the database that stores IP pools and configuration attributes. If it contains a password, make sure to adjust the permissions of the config file accordingly.|

|pool.load                                          |          |Plugins to load in ipsec pool tool.|

|\3(level1). *pt-tls-client section*                |

|pt-tls-client.load                                 |          |Plugins to load in ipsec pt-tls-client tool.|

|\3(level1). *scepclient section*                   |

|scepclient.load                                    |          |Plugins to load in ipsec scepclient tool.|

|\3(level1). *starter section*                      |

|starter.load                                       |          |Plugins to load in starter.|

|starter.load_warning                               |yes       |Show _charon.load_ setting warning, see [[PluginLoad]].|