Looks like the same poorly implemented Android CT library that broke a lot of apps a couple years ago... did it again 🤦♂️
https://github.com/appmattus/certificatetransparency/issues/143#issuecomment-2993688741
Looks like the same poorly implemented Android CT library that broke a lot of apps a couple years ago... did it again 🤦♂️
https://github.com/appmattus/certificatetransparency/issues/143#issuecomment-2993688741
Amongst other things, there's an open source software supply chain story here.
This Android library with 174 stars and one maintainer has taken down Monday.com, Eventbrite (!!!), UPS, Kraken, Lowe's, YBS, IKEA, Agibank, iFood, PagBank, pago.ro, and Udemy.
Again, this is the same failure mode that caused outages in 2023.
https://github.com/appmattus/certificatetransparency/issues/143#issuecomment-2993753426
@filippo I've been building systems and processes to prevent exactly such issues at large companies (international but smaller than the mentioned ones).
It's also not really that hard. Most effort is on the side of needing someone to do the reviewing.
The rest is setting up e.g. an internal-only GitLab and creating an automatic pull-mirror (prevents history rewrites). Then you include it as git-submodule into your projects and each time you want to update to main again it has to be reviewed.
Keiner von denen schreibt seine Webseiten/Anwendungen selber.
Es ist bequem diese und jene Bibliothek zu nutzen, die aber wieder Abhängigkeiten von anderen Bibliotheken hat.
Wer kennt alle Abhängigkeiten bis ins letzte Glied?
Ich meine niemand.
@filippo
My favorite reply on that: "Who can we contact at Google regarding these issues?"
Contact at Google. Haha.
@filippo Best comment: 'If this library is so critical to your infrastructure, why are only two(!) people sponsoring it?'
And it is a good question.