denozord/strongswan-ext
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

added ikev2/rw-eap-ttls-phase2-piggyback scenario

Browse Source
This commit is contained in:
Andreas Steffen
2010-08-16 18:32:00 +02:00
parent 9ba53310ee
commit cf95e162f2
14 changed files with 170 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/ikev2/rw-eap-ttls-phase2-piggyback/description.txt
+8
View File
@@ -0,0 +1,8 @@
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). The server <b>moon</b>
piggybacks the tunneled EAP Identity request which starts phase2 of EAP-TTLS right onto
the TLS Finished message. <b>carol</b> presents the correct MD5 password and succeeds
whereas <b>dave</b> chooses the wrong password and fails.