From f9b5d9ae9c3cfadabbe53a03b0c4284d004ebdec Mon Sep 17 00:00:00 2001 From: Andreas Steffen Date: Wed, 15 Jun 2011 14:07:16 +0200 Subject: [PATCH] fixed some descriptions --- testing/tests/tnc/tnccs-11-fhh/description.txt | 4 +--- testing/tests/tnc/tnccs-11-radius-block/description.txt | 7 +++---- testing/tests/tnc/tnccs-11-radius/description.txt | 7 +++---- testing/tests/tnc/tnccs-11/description.txt | 2 +- testing/tests/tnc/tnccs-20-block/description.txt | 2 +- testing/tests/tnc/tnccs-20-fhh/description.txt | 5 ++--- testing/tests/tnc/tnccs-20-tls/description.txt | 2 +- testing/tests/tnc/tnccs-20/description.txt | 2 +- 8 files changed, 13 insertions(+), 18 deletions(-) diff --git a/testing/tests/tnc/tnccs-11-fhh/description.txt b/testing/tests/tnc/tnccs-11-fhh/description.txt index 406b163e1..2b7545f59 100644 --- a/testing/tests/tnc/tnccs-11-fhh/description.txt +++ b/testing/tests/tnc/tnccs-11-fhh/description.txt @@ -3,9 +3,7 @@ using EAP-TTLS authentication only with the gateway presenting a server certific 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 health of carol and dave via the IF-TNCCS 1.1 client-server interface. -The Dummy IMC and IMV from the - -TNC@FHH project are used which communicate over a proprietary protocol. +The Dummy IMC and IMV from the TNC@FHH project are used which communicate over a proprietary protocol.

carol passes the health test and dave fails. Based on these measurements the clients are connected by gateway moon to the "rw-allow" and "rw-isolate" subnets, diff --git a/testing/tests/tnc/tnccs-11-radius-block/description.txt b/testing/tests/tnc/tnccs-11-radius-block/description.txt index d665b1364..ac24add7e 100644 --- a/testing/tests/tnc/tnccs-11-radius-block/description.txt +++ b/testing/tests/tnc/tnccs-11-radius-block/description.txt @@ -1,13 +1,12 @@ The roadwarriors carol and dave set up a connection each to gateway moon. At the outset the gateway authenticates itself to the clients by sending an IKEv2 RSA signature accompanied by a certificate. -carol and dave then set up an EAP-TTLS tunnel each via moon to the - -TNC@FHH-enhanced FreeRADIUS server alice authenticated by an X.509 AAA certificate. +carol and dave then set up an EAP-TTLS tunnel each via moon to +the FreeRADIUS server alice authenticated by an X.509 AAA certificate. The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on EAP-MD5. In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the health of carol and dave via the IF-TNCCS 1.1 client-server interface. -The IMC and IMV communicate using the IF-M protocol defined by RFC 5792 PA-TNC. +The IMC and IMV communicate are using the IF-M protocol defined by RFC 5792 PA-TNC.

carol passes the health test and dave fails. Based on these measurements carol is authenticated successfully and is granted access to the subnet behind moon whereas diff --git a/testing/tests/tnc/tnccs-11-radius/description.txt b/testing/tests/tnc/tnccs-11-radius/description.txt index 42651cc8a..127951239 100644 --- a/testing/tests/tnc/tnccs-11-radius/description.txt +++ b/testing/tests/tnc/tnccs-11-radius/description.txt @@ -1,13 +1,12 @@ The roadwarriors carol and dave set up a connection each to gateway moon. At the outset the gateway authenticates itself to the clients by sending an IKEv2 RSA signature accompanied by a certificate. -carol and dave then set up an EAP-TTLS tunnel each via moon to the - -TNC@FHH-enhanced FreeRADIUS server alice authenticated by an X.509 AAA certificate. +carol and dave then set up an EAP-TTLS tunnel each via moon to +the FreeRADIUS server alice authenticated by an X.509 AAA certificate. The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on EAP-MD5. In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the health of carol and dave via the IF-TNCCS 1.1 client-server interface. -The IMC and IMV communicate using the IF-M protocol defined by RFC 5792 PA-TNC. +The IMC and IMV communicate are using the IF-M protocol defined by RFC 5792 PA-TNC.

carol passes the health test and dave fails. Based on these measurements the clients are connected by gateway moon to the "rw-allow" and "rw-isolate" subnets, respectively. diff --git a/testing/tests/tnc/tnccs-11/description.txt b/testing/tests/tnc/tnccs-11/description.txt index d6a3ba283..2310a6747 100644 --- a/testing/tests/tnc/tnccs-11/description.txt +++ b/testing/tests/tnc/tnccs-11/description.txt @@ -3,7 +3,7 @@ using EAP-TTLS authentication only with the gateway presenting a server certific 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 health of carol and dave via the IF-TNCCS 1.1 client-server interface. -The IMC and IMV communicate using the IF-M protocol defined by RFC 5792 PA-TNC. +The IMC and IMV communicate are using the IF-M protocol defined by RFC 5792 PA-TNC.

carol passes the health test and dave fails. Based on these measurements the clients are connected by gateway moon to the "rw-allow" and "rw-isolate" subnets, diff --git a/testing/tests/tnc/tnccs-20-block/description.txt b/testing/tests/tnc/tnccs-20-block/description.txt index d240d5749..425496174 100644 --- a/testing/tests/tnc/tnccs-20-block/description.txt +++ b/testing/tests/tnc/tnccs-20-block/description.txt @@ -3,7 +3,7 @@ using EAP-TTLS authentication only with the gateway presenting a server certific 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 health of carol and dave via the IF-TNCCS 2.0 client-server interface -compliant with RFC 5793 PB-TNC. The IMC and IMV communicate using the IF-M +compliant with RFC 5793 PB-TNC. The IMC and IMV communicate are using the IF-M protocol defined by RFC 5792 PA-TNC.

carol passes the health test and dave fails. Based on these measurements diff --git a/testing/tests/tnc/tnccs-20-fhh/description.txt b/testing/tests/tnc/tnccs-20-fhh/description.txt index e68f363bb..798ba0034 100644 --- a/testing/tests/tnc/tnccs-20-fhh/description.txt +++ b/testing/tests/tnc/tnccs-20-fhh/description.txt @@ -3,9 +3,8 @@ using EAP-TTLS authentication only with the gateway presenting a server certific 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 health of carol and dave via the TNCCS 2.0 client-server interface -compliant with RFC 5793 PB-TNC. The Dummy IMC and IMV from the - -TNC@FHH project are used which communicate over a proprietary protocol. +compliant with RFC 5793 PB-TNC. The Dummy IMC and IMV from the TNC@FHH project are +used which communicate over a proprietary protocol.

carol passes the health test and dave fails. Based on these measurements the clients are connected by gateway moon to the "rw-allow" and "rw-isolate" subnets, diff --git a/testing/tests/tnc/tnccs-20-tls/description.txt b/testing/tests/tnc/tnccs-20-tls/description.txt index a520b40d2..a032d2d05 100644 --- a/testing/tests/tnc/tnccs-20-tls/description.txt +++ b/testing/tests/tnc/tnccs-20-tls/description.txt @@ -2,7 +2,7 @@ The roadwarriors carol and dave set up a connection each to gatewa both ends doing certificate-based EAP-TLS authentication only. In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the health of carol and dave via the IF-TNCCS 2.0 client-server interface -compliant with RFC 5793 PB-TNC. The IMC and IMV communicate using the IF-M +compliant with RFC 5793 PB-TNC. The IMC and IMV communicate are using the IF-M protocol defined by RFC 5792 PA-TNC.

carol passes the health test and dave fails. Based on these measurements the diff --git a/testing/tests/tnc/tnccs-20/description.txt b/testing/tests/tnc/tnccs-20/description.txt index 00c88eaa6..89f2845a9 100644 --- a/testing/tests/tnc/tnccs-20/description.txt +++ b/testing/tests/tnc/tnccs-20/description.txt @@ -3,7 +3,7 @@ using EAP-TTLS authentication only with the gateway presenting a server certific 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 health of carol and dave via the TNCCS 2.0 client-server interface -compliant with RFC 5793 PB-TNC. The IMC and IMV communicate using the IF-M +compliant with RFC 5793 PB-TNC. The IMC and IMV communicate are using the IF-M protocol defined by RFC 5792 PA-TNC.

carol passes the health test and dave fails. Based on these measurements the