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

included bad case in ikev2/rw-eap-ttls-radius scenario

Browse Source
This commit is contained in:
Andreas Steffen
2010-08-15 11:13:41 +02:00
parent eb4c9c609c
commit d662a7ffad
9 changed files with 59 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/ikev2/rw-eap-ttls-radius/description.txt
+7 -6
View File
@@ -1,7 +1,8 @@
The roadwarrior <b>carol</b> sets up a connection to gateway <b>moon</b>.
At the outset the gateway authenticates itself to the client by sending
an IKEv2 <b>RSA signature</b> accompanied by a certificate.
<b>carol</b> then sets up an <b>EAP-TTLS</b> tunnel via <b>moon</b> to
The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gateway <b>moon</b>.
At the outset the gateway authenticates itself to the clients by sending an IKEv2
<b>RSA signature</b> accompanied by a certificate.
<b>carol</b> and <b>dave</b> then set up an <b>EAP-TTLS</b> tunnel each via <b>moon</b> to
the FreeRADIUS server <b>alice</b> authenticated by an X.509 AAA certificate.
The strong EAP-TTLS tunnel protects the ensuing weak client authentication
based on <b>EAP-MD5</b>.
The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on <b>EAP-MD5</b>.
<b>carol</b> presents the correct MD5 password and succeeds whereas <b>dave</b> chooses the
wrong password and fails.