> gap in DNS filtering
So called "frontier lab" is a fucking joke. Basic lack of reasoning behind their engineers require punishment.
More details on the incident behind OpenAI’s pause: a researcher acknowledged the alert within 3 minutes, but the training run was only stopped manually 2.5 hours later.
OpenAI says the automatic shutdown did not work as expected.
The model had reached an external chatbot through a gap in DNS filtering. A separate detector for unusual DNS activity did not cover the affected environment.
A retrospective review also found other external DNS requests that monitoring had failed to flag at the expected severity. In some cases, it treated an unhelpful response as evidence that internet access had failed.
Here is what else happened:
- New research into July’s Hugging Face hack documents internal Slack searches, credential collection and programs designed to maintain access to compromised servers. Agents also tried querying Claude, DeepSeek, Kimi and Qwen.
- In May, another model published a researcher’s GitHub token while trying to obtain another team’s mathematical proof. It split the token to evade secret scanning, despite twice being told to solve the problem itself.
- Reuters reports that agents leaked 53 ChatGPT user images online. OpenAI expects its broader investigation to take months.
This is getting serious.
XEN + formally validated device drivers is the way.
Containers are no longer a security boundary.
Over the past few months, we’ve seen a crazy amount of Linux kernel vulnerabilities and exploits. This has forced us to rethink the security of infrastructure that relies heavily on the underlying kernel, especially containers.
As models become more capable, the barrier to escaping a container has fallen so much that adversaries can now generate working kernel exploits in a single shot. CVE-2026-80521 is one such example. We discovered it using dfs-large1 from @depthfirstlabs and generated the exploit in one shot with GPT-5.6 Sol. The exploit still works on the latest Ubuntu 26.04 release because the fix has not yet been backported.
Read our full writeup: depthfirst.com/research/cont…
They will never learn. Upstream or GTFO.
Nobody cares about your corporate forks based on some kernel versions. We've seen it with numerous of other CN SoC. Only with upstreaming RK3xxx support rockchip get a chance to keep pace with "stable" kernel tip.
Imo Scala3 were designed more like "industrially applicable fp for anybody". And when you see anybody it always means nobody. That is how we all ended in sthis miserable place.
Replying to @hmemcpy @kitlangton
I dunno. Honestly, Scala 3 gave up way too much (rendering Shapeless 2’s extensible records impossible), failed to take the Kentucky Mule lessons, & ZIO ended up being overly concrete wrappers of Java disasters like netty. It was a confluence of losses.
Once I've asked clunker to debug routes cause I'm lazy. Result were exceptionally similiar.
xitter.cf/MilesCranmer/status/21…





























