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.
22 lines
404 B
Plaintext
22 lines
404 B
Plaintext
# /etc/strongswan.conf - strongSwan configuration file
|
|
|
|
libimcv {
|
|
plugins {
|
|
imc-os {
|
|
push_info = no
|
|
}
|
|
imc-swid {
|
|
swid_directory = /usr/share
|
|
swid_pretty = yes
|
|
}
|
|
}
|
|
}
|
|
|
|
libtls {
|
|
suites = TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
|
|
}
|
|
|
|
pt-tls-client {
|
|
load = revocation constraints pem openssl curl nonce tnc-tnccs tnc-imc tnccs-20
|
|
}
|