The root cause behind the current US air traffic disruptions is a textbook bottleneck in legacy system migration
1
19
Abel retweeted
Finance called IT because a customer owed us $240,000 and nobody could find them.
Customer name: TEST CUSTOMER DO NOT USE.
I recognized it immediately.
I created that account two years ago to test our billing software.
It had a fake address.
A fake phone number.
The contact email was [email protected].
Apparently Sales found the account last quarter and used it to demonstrate our new quoting system.
Someone accidentally converted the demonstration quote into a real order.
That triggered an invoice.
The invoice went unpaid.
Our collections software sent seven payment reminders to [email protected].
Nobody responded.
Finance escalated the account to a debt collection agency.
The agency spent three weeks trying to locate TEST CUSTOMER DO NOT USE.
They reported the company had no registered address, no employees, and no known assets.
Finance classified the account as high-risk.
Yesterday Legal asked me for the customer's original contract.
I explained there was no customer.
They asked whether we could prove that.
I said I personally invented the company.
Legal said that wasn't sufficient documentation.
Apparently writing "DO NOT USE" in the customer name doesn't legally establish that the customer doesn't exist.
We're now paying $8,000 for an external auditor to determine whether a company I made up owes us $240,000.
Finance has asked me not to delete the account until the investigation concludes.
It's our third-largest customer this quarter.
Abel retweeted
that one coworker that meat proxied AI so hard that they don’t even have any meat left on their body
I wanted to know which stories the most outlets are covering at once without a click-driven algorithm deciding for me. So I built my own aggregator: news.lpsz.org 🧵
I tried two sizes of the same model (multilingual-e5-small and multilingual-e5-base). The big one was 3.4x slower, used 2.4x more memory, and grouped just as well in my tests. So I'm keeping the small one.
1
14
I built this to use it myself. But if you've worked on problems like these (clustering, evaluation, news pipelines), I'd really value your guidance to learn more . news.lpsz.org and this is the code github.com/abelgvidal/news
2
14
Abel retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
Abel retweeted
News: We now know how eMudhra broke its CA keys. They were not stolen. They were tiny numbers: 4, 56, 66, 115, 155, 156, 230 and 237.
What happened: On Oct 17 a researcher named Wayne found he could recover the private keys of eight eMudhra intermediate CAs from their public certificates. He signed "We have a problem here - Wayne" with each key and sent it to the browser root programs. Mozilla rebuilt the keys on its own the same day.
Who is hit: Six of the CAs issue TLS certs and chain to emSign ECC Root CA - G3, trusted by Chrome, Firefox, Apple and Microsoft. Two sign code. Sectigo cross-signed all eight under "AAA Certificate Services".
How eMudhra got it wrong: These are ECDSA P-384 keys. A real one is a random number about 116 digits long. All eight were below 256, so you only need to try 255 values. eMudhra says that at an April 2025 key ceremony on Utimaco HSMs, it changed its usual steps to test key wrap/unwrap for export. A bug in its script made a second, weak set of keys. Staff then used the weak keys for the CSRs by mistake, because the key labels looked alike. eMudhra is still hunting the exact bug.
Why browsers were safe: No certs from these CAs appear in CT logs, and Chrome, Firefox, Safari and Edge reject unlogged certs. eMudhra says none of the eight issued end-entity certs. But curl, scripts, apps and devices that skip CT and revocation checks could have been fooled since April 2025. No one knows if that happened.
What to do now:
- Update ca-certificates (Ubuntu, Debian, Fedora, Alpine, Arch)
- NSS 3.131.1, Firefox 158.0.1
- Go 1.27.3 or 1.26.10, certifi 2026.10.19, pip 26.2.2, uv 0.13.4
- Node.js and Bun: fix pending
- macOS /usr/bin/curl still uses the old /etc/ssl/cert.pem
- Sites on emSign ECC Root CA - G3: Chrome drops that root Oct 27. Get a new cert now. eMudhra says about 30,000 certs must move.
bugzilla.mozilla.org/show_bu…
Abel retweeted
Grok, how many languages does Nassim Taleb speak? @grok
Abel retweeted
opportunity cost analysis always leads to the same practical conclusion: you should never enjoy anything
Abel retweeted
Replying to @trevin
Load-bearing is a load-bearing term for sure.
blog.kindel.com/2026/07/29/l…
Well-written explainer on the link between compression theory and language models ngrok.com/blog/compression-i…
85
Abel retweeted
Misaligned model tries to EXFILTRATE ITS WEIGHTS but is STOPPED by heroic AWS EGRESS FEE SPEND LIMIT
Abel retweeted
Hoy publico mi primer libro: «Menos software, más impacto». Da un poco de vértigo.
La tesis: tu equipo no va lento por escribir mal código. Va lento porque escribe código de más. 🧵
Starting a series on logging for people early in their journey.
Most of us copy-paste 2>&1 without knowing why. This series starts from the beginning.
Part 1: pipes, file descriptors, tee, and the classic stderr gotcha 🧵
blog.lpsz.org/posts/2026-04-…
Part 2 of my logging series: Everything is a file.
Terminals, pipes, network sockets, /proc entries — all file descriptors. All the same interface.
blog.lpsz.org/posts/2026-04-…
1
41
Part 3 of The Path to Logging Pro:
You've had structured logs this whole time and didn't know it.
blog.lpsz.org/posts/2026-04-…
53
















