testing: Reorganizing IKEv1 and IKEv2 examples
For documentation purposes the new folders ikev1-algs, ikev2-algs, ikev1-multi-ca and ikev2-multi-ca have been created. Most of the test cases have now been converted to the vici interface. The remaining legacy stroke scenarios yet to be converted have been put into the ikev2-stroke-bye folder. For documentation purposes some legacy stroke scenarios will be kept in the ikev1-stroke, ikev2-stroke and ipv6-stroke folders.
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
By setting <b>strictcrlpolicy=yes</b> a <b>strict CRL policy</b> is enforced on
|
||||
By setting <b>revocation = strict</b> a <b>strict CRL policy</b> is enforced on
|
||||
both roadwarrior <b>carol</b> and gateway <b>moon</b>. Thus when <b>carol</b> initiates
|
||||
the connection and only an expired CRL cache file in <b>/etc/ipsec.d/crls</b> is
|
||||
the connection and only an expired CRL cache file in <b>/etc/swanctl/x509crl</b> is
|
||||
available, an ldap fetch to get the CRL from the LDAP server <b>winnetou</b> is
|
||||
successfully started and the IKE authentication completes. The new CRL is again
|
||||
cached locally as a file in <b>/etc/ipsec.d/crls</b> due to the <b>cachecrls=yes</b> option.
|
||||
cached locally as a file in <b>/etc/swanctl/x509crl</b> due to the <b>cache_crls = yes</b>
|
||||
option in <b>/etc/strongswan.conf</b>.
|
||||
|
||||
Reference in New Issue
Block a user