Signing inconsistent STHs is the worst kind of CT log misbehavior and leads to immediate disqualification by Chrome. That's what Venafi did.
-
-
-
In simpler terms, Venafi violated the append-only property and removed certs it had previously logged.
-
Venafi says log fork caused by restoration of stale backup from S3. Their Gen2 log server has better architecture.https://groups.google.com/a/chromium.org/d/msg/ct-policy/ohtZ64gLN3I/namq_NDmAQAJ …
End of conversation
New conversation -
-
-
To be clear, we have confirmed that NO certificate data has been lost.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
While the log server is functioning as expected now, we had a database inconsistency issue as part of the effort to get back online.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Venafi is aware of an issue that affected our certificate transparency log that originated when an outage affected AWS S3.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.