diff options
author | Andreas Steffen <andreas.steffen@strongswan.org> | 2012-03-14 08:46:52 +0100 |
---|---|---|
committer | Andreas Steffen <andreas.steffen@strongswan.org> | 2012-03-14 08:46:52 +0100 |
commit | 9b8053a63a532fef1d3b4899e02e91d81c6e4e80 (patch) | |
tree | b14061e6017c9f220911ad3f4360f3d12bb2958c /testing | |
parent | fb5450a435e7067786033f45edb42b7ef97f2af2 (diff) | |
download | strongswan-9b8053a63a532fef1d3b4899e02e91d81c6e4e80.tar.bz2 strongswan-9b8053a63a532fef1d3b4899e02e91d81c6e4e80.tar.xz |
edited description of tnc/tnccs-11-radius scenario
Diffstat (limited to 'testing')
-rw-r--r-- | testing/tests/tnc/tnccs-11-radius/description.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/testing/tests/tnc/tnccs-11-radius/description.txt b/testing/tests/tnc/tnccs-11-radius/description.txt index 46ed5f584..83e5b96f3 100644 --- a/testing/tests/tnc/tnccs-11-radius/description.txt +++ b/testing/tests/tnc/tnccs-11-radius/description.txt @@ -7,7 +7,7 @@ At the outset the gateway authenticates itself to the clients by sending an IKEv The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on <b>EAP-MD5</b>. 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>IF-TNCCS 1.1</b> client-server interface. -The IMC and IMV communicate are using the <b>IF-M</b> protocol defined by <b>RFC 5792 PA-TNC</b>. +The communication between IMCs and IMVs is based on the <b>IF-M</b> protocol defined by <b>RFC 5792 PA-TNC</b>. <p> <b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements the clients are connected by gateway <b>moon</b> to the "rw-allow" and "rw-isolate" subnets, respectively. |