Here is a write-up on regarding the issue, which if I understand the 'problem' as presented therein, any device/browser/os config that is really choosy about SSL cert validity might be affected. It's possible that your security posture on your firewall may be a factor, such as whether you are doing deep ssl inspection and what other policies are in place in that area. I was asking to kind of get a feel of whether this was something the other firewall manufactures were unaffected by, maybe because they got ahead of it with updated cert bundles previously.

We checked on search engines to see if others had similar issues and I saw a lot of chatter about Fortigates, but not a whole lot from other manufacturers. įortinet is releasing an updated Certificate Bundle that would be a permanent solution, but has been slow in releasing that as they test it. mine is highly regulated line of business so we are averse to weakening security posture, and our critical vendors are using enterprise-grade SSL certs from the big guys (entrust, digicert, etc) so we have not yet decided it was practical to weaken our posture due to this issue since this seems to be centered around SSLs issued by. Whether those are acceptable but depend on your line of business. I'll admit there are some workarounds for the Fortinet sphere, but in general the workarounds in my opinion weaken security posture (eg, ignoring invalid certs is one workaround, ignoring expired certs is another workaround, and lastly switching from proxy to passthrough to let the browser decide if it is ok with the cert validity).

Avast blocking sites with valid certs