openssl-ikev2/rw-cert scenario doesn't need x509 plugin any more

2010-05-25 15:26:46 +02:00
parent e2bd6b616e
commit 2996cb3163
3 changed files with 5 additions and 5 deletions
@@ -1,7 +1,7 @@
 The roadwarrior <b>carol</b> and the gateway <b>moon</b> use the <b>openssl</b>
-plugin based on the <b>OpenSSL</b> library for all cryptographical functions
+plugin based on the <b>OpenSSL</b> library for all cryptographical and X.509 certificate
-whereas roadwarrior <b>dave</b> uses the default <b>strongSwan</b> cryptographical
+functions whereas roadwarrior <b>dave</b> uses the default <b>strongSwan</b> cryptographical
-plugins <b>aes des sha1 sha2 md5 gmp</b>.
+plugins <b>aes des sha1 sha2 md5 gmp</b> and <b>x509</b>.
 <p>
 The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each 
 to gateway <b>moon</b>. The authentication is based on <b>X.509 certificates</b>.
@@ -1,7 +1,7 @@
 # /etc/strongswan.conf - strongSwan configuration file
 charon {
-  load = curl test-vectors pem pkcs1 openssl random x509 hmac stroke kernel-netlink socket-default updown
+  load = curl test-vectors pem pkcs1 openssl random hmac stroke kernel-netlink socket-default updown
 }
 libstrongswan {
@@ -1,7 +1,7 @@
 # /etc/strongswan.conf - strongSwan configuration file
 charon {
-  load = curl test-vectors pem pkcs1 openssl random x509 hmac stroke kernel-netlink socket-default updown
+  load = curl test-vectors pem pkcs1 openssl random hmac stroke kernel-netlink socket-default updown
 }
 libstrongswan {