Files
strongswan-ext/testing/tests/ikev2/strong-keys-certs/description.txt
T
Andreas Steffen 7c5a2974b9 testing: Reorganizing IKEv1 and IKEv2 examples
For documentation purposes the new folders ikev1-algs, ikev2-algs,
ikev1-multi-ca and ikev2-multi-ca have been created. Most of the
test cases have now been converted to the vici interface. The
remaining legacy stroke scenarios yet to be converted have been put
into the ikev2-stroke-bye folder.

For documentation purposes some legacy stroke scenarios will be kept
in the ikev1-stroke, ikev2-stroke and ipv6-stroke folders.
2021-05-21 09:42:50 +02:00

12 lines
740 B
Plaintext
Executable File

The gateway <b>moon</b> uses a 3072 bit RSA private key protected by <b>AES-128</b>
encryption whereas the roadwarriors <b>carol</b> and <b>dave</b> have an
<b>AES-192</b> and <b>AES-256</b> envelope, respectively.
The X.509 certificate of the gateway <b>moon</b> uses a <b>SHA-224</b> hash in
its signature whereas the certificates of the roadwarriors <b>carol</b>
and <b>dave</b> use <b>SHA-384</b> and <b>SHA-512</b>, respectively.
<p/>
Upon the successful establishment of the IPsec tunnels, the updown script
automatically inserts iptables-based firewall rules that let pass the tunneled traffic.
In order to test both tunnel and firewall, both <b>carol</b> and <b>dave</b> ping
the client <b>alice</b> behind the gateway <b>moon</b>.