Annotation of embedaddon/strongswan/testing/tests/swanctl/rw-eap-peap-md5/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-PEAP</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-PEAP). This tunnel protects the ensuing weak client
5: authentication based on <b>EAP-MD5</b> (phase2 of EAP-PEAP).
6: <p/>
7: With the setting <b>charon.plugins.eap-peap.phase2_piggyback = yes</b> the server <b>moon</b>
8: initiates phase2 of the EAP-PEAP protocol by piggybacking a tunneled EAP Identity request
9: right onto the TLS Finished message. Client <b>carol</b> presents the correct MD5 password
10: and succeeds whereas client <b>dave</b> chooses the wrong password and fails.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>