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

renamed tncss-20-retry scenario to tnccs-20-client-retry

Browse Source
This commit is contained in:
Andreas Steffen
2011-06-23 19:59:00 +02:00
parent 7401269517
commit 6b57728cce
17 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/tnc/tnccs-20-client-retry/description.txt
+13
View File
@@ -0,0 +1,13 @@
The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gateway <b>moon</b>
using EAP-TTLS authentication only with the gateway presenting a server certificate and
the clients doing EAP-MD5 password-based authentication.
In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
health of <b>carol</b> and <b>dave</b> via the <b>TNCCS 2.0 </b> client-server interface
compliant with <b>RFC 5793 PB-TNC</b>. The IMC and IMV communicate are using the <b>IF-M</b>
protocol defined by <b>RFC 5792 PA-TNC</b>.
<p>
The first time around both <b>carol</b> and <b>dave</b> fail the health test but they
request a handshake retry. After remediation <b>carol</b> succeeds but <b>dave</b>
still fails. Thus based on this second round of measurements the clients are connected
by gateway <b>moon</b> to the "rw-allow" and "rw-isolate" subnets, respectively.
</p>