Martin Willi
44b6a34d43
Some fetcher plugins (such as curl) might build upon OpenSSL to implement HTTPS fetching. As we set (and can't unset) threading callbacks in our openssl plugin, we must ensure that OpenSSL functions don't get called after openssl plugin unloading. We achieve that by loading curl and all other fetcher plugins after the base crypto plugins, including openssl.
30 lines
641 B
Plaintext
30 lines
641 B
Plaintext
# /etc/strongswan.conf - strongSwan configuration file
|
|
|
|
charon {
|
|
load = pem pkcs1 nonce x509 openssl curl revocation constraints socket-default kernel-netlink stroke tnc-pdp tnc-imv tnc-tnccs tnccs-20 sqlite
|
|
|
|
plugins {
|
|
tnc-pdp {
|
|
server = aaa.strongswan.org
|
|
radius {
|
|
secret = gv6URkSs
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|
|
libtls {
|
|
suites = TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
|
|
}
|
|
|
|
libimcv {
|
|
database = sqlite:///etc/pts/config.db
|
|
policy_script = ipsec imv_policy_manager
|
|
|
|
plugins {
|
|
imv-swid {
|
|
rest_api_uri = http://admin-user:[email protected]/api/
|
|
}
|
|
}
|
|
}
|