aboutsummaryrefslogtreecommitdiffstats
path: root/testing/tests/tnc/tnccs-11-radius-pts
diff options
context:
space:
mode:
authorAndreas Steffen <andreas.steffen@strongswan.org>2013-07-19 19:36:07 +0200
committerAndreas Steffen <andreas.steffen@strongswan.org>2013-07-19 19:36:07 +0200
commit645e9291f03a4d4714a1e27d8fea83643f6cb48a (patch)
tree58fd348af19c73cc2828140d147d1d99e936ba59 /testing/tests/tnc/tnccs-11-radius-pts
parentdcd5129c2524401ebc0e566bfd389157e61d31f6 (diff)
downloadstrongswan-645e9291f03a4d4714a1e27d8fea83643f6cb48a.tar.bz2
strongswan-645e9291f03a4d4714a1e27d8fea83643f6cb48a.tar.xz
updated some TNC scenarios
Diffstat (limited to 'testing/tests/tnc/tnccs-11-radius-pts')
-rw-r--r--testing/tests/tnc/tnccs-11-radius-pts/description.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/testing/tests/tnc/tnccs-11-radius-pts/description.txt b/testing/tests/tnc/tnccs-11-radius-pts/description.txt
index 83e5b96f3..51dd03362 100644
--- a/testing/tests/tnc/tnccs-11-radius-pts/description.txt
+++ b/testing/tests/tnc/tnccs-11-radius-pts/description.txt
@@ -7,7 +7,8 @@ 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 communication between IMCs and IMVs is based on the <b>IF-M</b> protocol defined by <b>RFC 5792 PA-TNC</b>.
+The communication between the OS and Attestation IMC and the Attestion IMV 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.