Good: Let’s Encrypt botched issuance of 645 certificates during a configuration change. A combination of factors led to the creation of certificates that were not substantially the same as their corresponding precertificates. Read more about the problem in the incident report. There’s also a blog post from Andrew Ayer, who discovered the problem within minutes. We classify this as good based on the combination of community monitoring that led to near-immediate discovery of the problem and Let’s Encrypt’s fast reaction, transparency, and in-depth incident report.
9 Likes
I'm not familiar with Feisty Duck, but what kind of /ls/click?upn=bunch_of_stuff kind of URL is THAT? Personally that's not a link I'd click on to be honest.
2 Likes
Perhaps a better link:
https://www.feistyduck.com/bulletproof-tls-newsletter/issue_102_four_ca_stories_the_good_times_two_the_bad_and%20the_ugly
The article is from the Bulletproof TLS Newsletter authored by Ivan Ristić of SSL Labs fame.
10 Likes
That link looks a lot better indeed, thanks 
6 Likes
@Nekit beat you to the punch!
I'd say, use:
https://www.feistyduck.com/bulletproof-tls-newsletter/
As it is the latest entry, it will show there.
For those who may be reading this... [much] later, it's Issue #102 [click on that one]
5 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.