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.
33 lines
727 B
Plaintext
33 lines
727 B
Plaintext
# /etc/strongswan.conf - strongSwan configuration file
|
|
|
|
charon {
|
|
load = aes md5 sha1 sha2 hmac gmp pem pkcs1 random nonce x509 curl revocation stroke kernel-netlink socket-default eap-identity eap-ttls eap-md5 eap-tnc tnc-imv tnc-tnccs tnccs-20 updown sqlite
|
|
|
|
multiple_authentication = no
|
|
|
|
plugins {
|
|
eap-ttls {
|
|
phase2_method = md5
|
|
phase2_piggyback = yes
|
|
phase2_tnc = yes
|
|
}
|
|
}
|
|
}
|
|
|
|
libimcv {
|
|
database = sqlite:///etc/pts/config.db
|
|
policy_script = ipsec imv_policy_manager
|
|
plugins {
|
|
imv-attestation {
|
|
hash_algorithm = sha1
|
|
dh_group = modp2048
|
|
mandatory_dh_groups = no
|
|
}
|
|
}
|
|
}
|
|
|
|
attest {
|
|
load = random nonce openssl sqlite
|
|
database = sqlite:///etc/pts/config.db
|
|
}
|