Re: [strongSwan] Strongswan caching CRL's when setting is set to "no"

Does ".reauth_time” and leaving “break_before_make” alone force a reauth and certificate validity check on IKE/ISAKMP from non-cached crl’s? Apologies for all the questions. Eric > On Jun 1, 2022, at 10:43 AM, Tobias Brunner wrote: > > Hi Eric, > >> 16[IKE] received end entity cert "CN=pfse

Re: [strongSwan] Strongswan caching CRL's when setting is set to "no"

Hi Eric, 16[IKE] received end entity cert "CN=pfsense.semperen.net , C=US, ST=OH, L=Van Wert, O=The Semperen Group, OU=Network Operations" 16[CFG]   using certificate "CN=pfsense.semperen.net , C=US, ST=OH, L=Van Wert, O=The Semperen G

Re: [strongSwan] Strongswan caching CRL's when setting is set to "no"

crluri = "https://ipsec-crl.s3.us-east-2.amazonaws.com/Semperen%2BIPSec%2BSigning%2BAuthority%2BCRL.crl"; 16[IKE] received end entity cert "CN=pfsense.semperen.net, C=US, ST=OH, L=Van Wert, O=The Semperen Group, OU=Network Operations" 16[CFG] using certificate "CN=pfsense.s

Re: [strongSwan] Strongswan caching CRL's when setting is set to "no"

Hi Eric, What's the point of SS having an option to auto fetch a CRL at startup There is no such option. Regards, Tobias