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

testing: Added swanctl/ocsp-disabled scenario

Browse Source
This commit is contained in:
Andreas Steffen
2017-01-02 14:34:39 +01:00
parent db0953d41f
commit 91a4a4aa83
11 changed files with 264 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/tests/swanctl/ocsp-disabled/description.txt
+10
View File
@@ -0,0 +1,10 @@
By setting <b>strictcrlpolicy=yes</b>, a <b>strict</b> CRL policy is enforced on
both roadwarrior <b>carol</b> and gateway <b>moon</b>.
Client <b>carol</b>'s certificate includes an <b>OCSP URI</b> in an authority information
access extension pointing to <b>winnetou</b>. Gateway <b>moon</b>'s certificate doesn't
contain any such extensions but <b>carol</b>'s swanctl.conf contains a corresponding
authorities section. With the directive <b>charon.plugins.revocation.enable_ocsp = no</b>
in strongswan.conf all OCSP fetching is disabled and a fallback to CRL fetching occurs.
<p/>
<b>carol</b> can successfully initiate an IPsec connection to <b>moon</b> since
the status of both certificates is <b>good</b>.