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

testing: Fix URL to TNC@FHH project in scenario descriptions

Browse Source
This commit is contained in:
Tobias Brunner
2015-05-05 11:48:56 +02:00
parent 41e9a261ac
commit 966efbc10d
6 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/tnc/tnccs-11-fhh/description.txt
+1 -1
View File
@@ -4,7 +4,7 @@ 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 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. health of <b>carol</b> and <b>dave</b> via the <b>IF-TNCCS 1.1</b> client-server interface.
The Dummy IMC and IMV from the The Dummy IMC and IMV from the
<a href="http://trust.inform.fh-hannover.de/joomla/index.php/projects/tncfhh" target="popup"> <a href="http://trust.f4.hs-hannover.de/projects/tncatfhh.html" target="popup">
<b>TNC@FHH</b></a> project are used which communicate over a proprietary protocol. <b>TNC@FHH</b></a> project are used which communicate over a proprietary protocol.
<p> <p>
<b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements the <b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements the
testing/tests/tnc/tnccs-11-radius-block/description.txt
+2 -2
View File
@@ -2,7 +2,7 @@ The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gatewa
At the outset the gateway authenticates itself to the clients by sending an IKEv2 At the outset the gateway authenticates itself to the clients by sending an IKEv2
<b>RSA signature</b> accompanied by a certificate. <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 <b>moon</b> to the <b>carol</b> and <b>dave</b> then set up an <b>EAP-TTLS</b> tunnel each via <b>moon</b> to the
<a href="http://trust.inform.fh-hannover.de/joomla/index.php/projects/tncfhh" target="popup"> <a href="http://trust.f4.hs-hannover.de/projects/tncatfhh.html" target="popup">
<b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated by an X.509 AAA certificate. <b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated by an X.509 AAA certificate.
The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on <b>EAP-MD5</b>. 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 In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
@@ -10,5 +10,5 @@ health of <b>carol</b> and <b>dave</b> via the <b>IF-TNCCS 1.1</b> client-server
The IMC and IMV communicate are using the <b>IF-M</b> protocol defined by <b>RFC 5792 PA-TNC</b>. The IMC and IMV communicate are using the <b>IF-M</b> protocol defined by <b>RFC 5792 PA-TNC</b>.
<p> <p>
<b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements <b>carol</b> <b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements <b>carol</b>
is authenticated successfully and is granted access to the subnet behind <b>moon</b> whereas is authenticated successfully and is granted access to the subnet behind <b>moon</b> whereas
<b>dave</b> fails the layered EAP authentication and is rejected. <b>dave</b> fails the layered EAP authentication and is rejected.
testing/tests/tnc/tnccs-11-radius-pts/description.txt
+1 -1
View File
@@ -2,7 +2,7 @@ The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gatewa
At the outset the gateway authenticates itself to the clients by sending an IKEv2 At the outset the gateway authenticates itself to the clients by sending an IKEv2
<b>RSA signature</b> accompanied by a certificate. <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 <b>moon</b> to the <b>carol</b> and <b>dave</b> then set up an <b>EAP-TTLS</b> tunnel each via <b>moon</b> to the
<a href="http://trust.inform.fh-hannover.de/joomla/index.php/projects/tncfhh" target="popup"> <a href="http://trust.f4.hs-hannover.de/projects/tncatfhh.html" target="popup">
<b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated by an X.509 AAA certificate. <b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated by an X.509 AAA certificate.
The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on <b>EAP-MD5</b>. 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 In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
testing/tests/tnc/tnccs-11-radius/description.txt
+1 -1
View File
@@ -2,7 +2,7 @@ The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gatewa
At the outset the gateway authenticates itself to the clients by sending an IKEv2 At the outset the gateway authenticates itself to the clients by sending an IKEv2
<b>RSA signature</b> accompanied by a certificate. <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 <b>moon</b> to the <b>carol</b> and <b>dave</b> then set up an <b>EAP-TTLS</b> tunnel each via <b>moon</b> to the
<a href="http://trust.inform.fh-hannover.de/joomla/index.php/projects/tncfhh" target="popup"> <a href="http://trust.f4.hs-hannover.de/projects/tncatfhh.html" target="popup">
<b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated by an X.509 AAA certificate. <b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated by an X.509 AAA certificate.
The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on <b>EAP-MD5</b>. 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 In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
testing/tests/tnc/tnccs-11-supplicant/description.txt
+1 -1
View File
@@ -1,7 +1,7 @@
The layer 2 supplicants <b>carol</b> and <b>dave</b> want to connect to a network The layer 2 supplicants <b>carol</b> and <b>dave</b> want to connect to a network
via switch <b>moon</b> which delegates the IEEE 802.1X authentication to the RADIUS via switch <b>moon</b> which delegates the IEEE 802.1X authentication to the RADIUS
server <b>alice</b>. <b>carol</b> and <b>dave</b> set up an <b>EAP-TTLS</b> tunnel server <b>alice</b>. <b>carol</b> and <b>dave</b> set up an <b>EAP-TTLS</b> tunnel
each via <b>moon</b> to the <a href="http://trust.inform.fh-hannover.de/joomla/index.php/projects/tncfhh" target="popup"> <b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated each via <b>moon</b> to the <a href="http://trust.f4.hs-hannover.de/projects/tncatfhh.html" target="popup"> <b>TNC@FHH</b></a>-enhanced FreeRADIUS server <b>alice</b> authenticated
by an X.509 AAA certificate. by an X.509 AAA certificate.
The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on <b>EAP-MD5</b>. 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 In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
testing/tests/tnc/tnccs-20-fhh/description.txt
+2 -2
View File
@@ -3,8 +3,8 @@ using EAP-TTLS authentication only with the gateway presenting a server certific
the clients doing EAP-MD5 password-based authentication. 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 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 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 Dummy IMC and IMV from the compliant with <b>RFC 5793 PB-TNC</b>. The Dummy IMC and IMV from the
<a href="http://trust.inform.fh-hannover.de/joomla/index.php/projects/tncfhh" target="popup"> <a href="http://trust.f4.hs-hannover.de/projects/tncatfhh.html" target="popup">
<b>TNC@FHH</b></a> project are used which communicate over a proprietary protocol. <b>TNC@FHH</b></a> project are used which communicate over a proprietary protocol.
<p> <p>
<b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements the <b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements the