testing: Migrated botan scenarios

This commit is contained in:
Andreas Steffen
2024-11-22 14:14:53 +01:00
committed by Tobias Brunner
parent 17e0f20f57
commit b9e5764b75
6 changed files with 13 additions and 13 deletions
@@ -1,8 +1,8 @@
The roadwarrior <b>carol</b> and the gateway <b>moon</b> use the <b>botan</b>
plugin based on the <b>Botan</b> library for all cryptographical functions whereas
roadwarrior <b>dave</b> uses the default <b>strongSwan</b> cryptographical
plugins. The authentication is based on <b>X.509 certificates</b> and the key exchange
on <b>modp3072</b>.
roadwarrior <b>dave</b> uses t<b>openssl</b> as the default <b>strongSwan</b>
cryptographical plugin. The authentication is based on <b>X.509 certificates</b>
and the key exchange on <b>modp3072</b>.
<p/>
Upon the successful establishment of the IPsec tunnels, the updown script
automatically inserts iptables-based firewall rules that let pass the tunneled traffic.
@@ -1,11 +1,11 @@
# /etc/strongswan.conf - strongSwan configuration file
swanctl {
load = pem pkcs1 x509 revocation constraints pubkey openssl random
load = pem pkcs1 revocation constraints pubkey openssl random
}
charon-systemd {
load = random nonce sha1 sha2 aes hmac kdf mgf1 pem pkcs1 x509 revocation constraints pubkey gmp curl kernel-netlink socket-default updown vici
load = random nonce openssl pem pkcs1 revocation constraints pubkey curl kernel-netlink socket-default updown vici
rsa_pss = yes
}