We could make the same change for charon (actually setting it for charon in strongswan.conf.testing would work for charon-systemd too), however, there are dozens of test cases that currently set charondebug in ipsec.conf.
35 lines
716 B
Plaintext
35 lines
716 B
Plaintext
# /etc/strongswan.conf - strongSwan configuration file
|
|
|
|
charon-systemd {
|
|
load = random nonce aes sha1 sha2 md5 pem pkcs1 gmp hmac x509 revocation curl vici socket-default kernel-netlink eap-identity eap-ttls eap-tnc tnc-pdp tnc-imv tnc-tnccs tnccs-20 sqlite
|
|
|
|
syslog {
|
|
daemon {
|
|
tnc = 2
|
|
imv = 3
|
|
}
|
|
}
|
|
plugins {
|
|
eap-ttls {
|
|
request_peer_auth = yes
|
|
phase2_piggyback = yes
|
|
phase2_tnc = yes
|
|
max_message_count = 0
|
|
}
|
|
eap-tnc {
|
|
max_message_count = 0
|
|
}
|
|
tnc-pdp {
|
|
server = aaa.strongswan.org
|
|
radius {
|
|
secret = gv6URkSs
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|
|
libimcv {
|
|
debug_level = 3
|
|
policy_script = /usr/local/libexec/ipsec/imv_policy_manager
|
|
}
|