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

added ikev2/rw-eap-peap-md5 scenario

Browse Source
This commit is contained in:
Andreas Steffen
2011-04-06 19:44:30 +02:00
parent 119b0a45a1
commit 35e2a87e1e
14 changed files with 169 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/ikev2/rw-eap-peap-md5/description.txt
+10
View File
@@ -0,0 +1,10 @@
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-PEAP</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-PEAP). This tunnel protects the ensuing weak client
authentication based on <b>EAP-MD5</b> (phase2 of EAP-PEAP).
<p/>
With the setting <b>charon.plugins.eap-peap.phase2_piggyback = yes</b> the server <b>moon</b>
initiates phase2 of the EAP-PEAP protocol by piggybacking a tunneled EAP Identity request
right onto the 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.