Andreas Steffen
7c5a2974b9
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.
12 lines
846 B
Plaintext
12 lines
846 B
Plaintext
The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gateway <b>moon</b>.
|
|
The strong mutual authentication is based on <b>EAP-TTLS</b> only (without a separate IKEv2
|
|
authentication) with the gateway being authenticated by a server certificate during the
|
|
EAP-TLS tunnel setup (phase1 of EAP-TTLS). This tunnel protects the ensuing weak client
|
|
authentication based on <b>EAP-MD5</b> (phase2 of EAP-TTLS).
|
|
<p/>
|
|
With the default setting <b>charon.plugins.eap-ttls.phase2_piggyback = no</b> the server
|
|
<b>moon</b> passively waits for the clients to initiate phase2 of the EAP-TTLS protocol by
|
|
sending a tunneled orphan EAP Identity response upon the reception of the server's TLS
|
|
Finished message. Client <b>carol</b> presents the correct MD5 password and succeeds
|
|
whereas client <b>dave</b> chooses the wrong password and fails.
|