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.
36 lines
791 B
Plaintext
36 lines
791 B
Plaintext
# /etc/strongswan.conf - strongSwan configuration file
|
|
|
|
charon {
|
|
load = aes des sha1 sha2 md5 pem pkcs1 gmp random nonce x509 curl revocation hmac socket-default kernel-netlink stroke eap-identity eap-ttls eap-md5 eap-tnc tnc-pdp tnc-imv tnc-tnccs tnccs-20 sqlite
|
|
|
|
plugins {
|
|
eap-ttls {
|
|
phase2_method = md5
|
|
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
|
|
database = sqlite:///etc/pts/config.db
|
|
policy_script = ipsec imv_policy_manager
|
|
|
|
plugins {
|
|
imv-swid {
|
|
rest_api_uri = http://admin-user:[email protected]/api/
|
|
}
|
|
}
|
|
}
|