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

testing: Added tnc/tnccs-20-hcd-eap scenario

Browse Source
This commit is contained in:
Andreas Steffen
2015-08-18 21:25:39 +02:00
parent 18472ac21c
commit ac28daac38
24 changed files with 674 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/tnc/tnccs-20-hcd-eap/description.txt
+11
View File
@@ -0,0 +1,11 @@
The hardcopy devices <b>carol</b> and <b>dave</b> set up a connection each to the policy enforcement
point <b>moon</b>. At the outset the gateway authenticates itself to the devices 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 gateway <b>moon</b> to the policy decision point <b>alice</b>
authenticated by an X.509 AAA certificate. 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 2.0</b>
client-server interface defined by <b>RFC 5793 PB-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>
The HCD IMC on the hardcopy devices <b>carol</b> and <b>dave</b> sends printer attributes to the HCD IMV
located on the RADIUS server <b>alice</b>. Because some mandatory HCD attributes are missing, the hardcopy devices <b>carol</b> and <b>dave</b> are blocked from accessing the network behind gateway <b>moon</b>.