Let’s Encrypt has become aware that during the resolution of Let's Encrypt: Gen Y Cross-Certified Subordinate CAs missing serverAuth EKU our ceremony tooling did not use the correct reason code due to software error. We had intended and configured our ceremony tooling to revoke with reason code 4: superseded.
We have filed a preliminary incident report at Let's Encrypt: Root CRLs Missing Reason Code; we will use this bug to communicate future updates including the full incident report.
Can you confirm whether or not this incident will likely involve needing to revoke leaf certificates? I'm assuming not (especially as the original incident didn't) but figured it can't hurt to double-check.
(Also, I would have expected this post to be in the Incidents category, while I'm on here a lot I have that category set to "watch" and email me about new posts, but not for this category.)
We have no plans to revoke leaf certificates as a result of this incident.
Thanks for noticing the incorrect category. I did not have "incidents" as an option, that should be fixed for me and on this post now. Oops!