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

Updated description of TNC scenarios concerning RFC 7171 PT-EAP support

Browse Source
This commit is contained in:
Andreas Steffen
2014-06-26 09:47:03 +02:00
parent 21aebe3781
commit 75598e5053
6 changed files with 30 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/tnc/tnccs-20-pts/description.txt
+4 -3
View File
@@ -1,12 +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
state of <b>carol</b>'s and <b>dave</b>'s operating system via the <b>TNCCS 2.0 </b>
<p/>
In a next step the <b>RFC 7171 PT-EAP</b> transport protocol is used within the EAP-TTLS tunnel
to determine the state of <b>carol</b>'s and <b>dave</b>'s operating system via the <b>TNCCS 2.0</b>
client-server interface compliant with <b>RFC 5793 PB-TNC</b>. The OS and Attestation IMCs
exchange PA-TNC attributes with the OS IMV via the <b>IF-M 1.0</b> measurement protocol
defined by <b>RFC 5792 PA-TNC</b>.
<p>
<p/>
<b>carol</b> sends information on her operating system consisting of the PA-TNC attributes
<em>Product Information</em>, <em>String Version</em>, and <em>Device ID</em> up-front
to the Attestation IMV, whereas <b>dave</b> must be prompted by the IMV to do so via an