Annotation of embedaddon/strongswan/testing/tests/ikev2/rw-eap-ttls-only/description.txt, revision 1.1.1.1
1.1 misho 1: The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gateway <b>moon</b>.
2: The strong mutual authentication is based on <b>EAP-TTLS</b> only (without a separate IKEv2
3: authentication) with the gateway being authenticated by a server certificate during the
4: EAP-TLS tunnel setup (phase1 of EAP-TTLS). This tunnel protects the ensuing weak client
5: authentication based on <b>EAP-MD5</b> (phase2 of EAP-TTLS).
6: <p/>
7: With the default setting <b>charon.plugins.eap-ttls.phase2_piggyback = no</b> the server
8: <b>moon</b> passively waits for the clients to initiate phase2 of the EAP-TTLS protocol by
9: sending a tunneled orphan EAP Identity response upon the reception of the server's TLS
10: Finished message. Client <b>carol</b> presents the correct MD5 password and succeeds
11: whereas client <b>dave</b> chooses the wrong password and fails.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>