On September 8, 2017, a member our team discovered that one of our OCSP
responder certificates had been signed with SHA-1 with a notBefore date of May
23, 2017. We initiated an investigation and discovered that there were a total
of 4 such certificates, all issued on May 23 as annual renewals
On 07/09/17 00:41, Ben Wilson wrote:
> We immediately contacted the operators of the issuing CAs and
> requested that they replace their OCSP responder certificates with
> ones signed with SHA2, and most have done so. However, in drafting
> this post I reviewed the Baseline Requirements, section
2 matches
Mail list logo
