8,738 karma · joined April 2, 2009
[ my public key: https://keybase.io/cgamesplay; my proof: https://keybase.io/cgamesplay/sigs/GtbWedLQcajnhwIFcwX1AsuUul7jHmox7E_MCW6PHlw ]
Can you name some of these JS engine vulnerabilities? And the PHP one had nothing to do with JIT.
So from the perspective of hacking old IoT devices, if your device hasn't been updated since 2018, the AAA path should work; if since February 2025, either path works; if since October 2026, the emSign path.
No, the article listed some apps that were not vulnerable, and the first question to me is “so what is vulnerable?” And the answer is “every curl | sh installer on the internet since April 2025” (among assuredly many other less prolific apps).
> This would have been possible since the certificates were created in April 2025. ... CT-enforcing clients like Firefox, Chrome, Edge and Safari could not have been attacked.
Meanwhile, back in April 2025: "Is it possible to enable CT checks in curl?" "No." https://github.com/curl/curl/discussions/17078
For each project, I define "review surfaces": parts of the code that I have a strong opinion about. These get resolved in detail before implementation begins; the LLM can do whatever it wants to other parts of the code, but the parts I list can't change without another review. Typically, these are things like the public API or database schema.
A lot of which is fake "grassroots" movements by... foreign actors. This isn't new:
- 2021: https://cloud.google.com/blog/topics/threat-intelligence/pro...
- 2022: https://cloud.google.com/blog/topics/threat-intelligence/dra...
I might pick one of these up in the de-Googled variant and keep my iPhone around for all the "attestation required to view your bank balance" apps that I have.
This is a terrible analogy, because yes you absolutely do hold the trainers criminally liable when they bite somebody else's face.
> In the simplest of terms, with the bug, if you created a new APFS (Apple File System) encrypted volume on High Sierra, and set anything at all as the password hint, then your password was stored as the hint. In plain text.
But this begs the question, why is cgit scanning 340 MB to answer this question? Is cgit not using good indexes? (Making a space-time tradeoff that doesn't make sense on a public-access website in a post-stupid-AI-scraper world?)
2. Why would you need a full clone to access /blob/cee9395acd8043be0644b25c34bfa86623f2b935/block/badblocks.c?
It feels like turning these frontends into JS-only viewers would resolve this, for the most part. The JS clones the repo in memory and renders whatever lens the requestor wants, and the server becomes a dumb object storage that uses less resources. The anti-JS folks are free to clone the repo still, and view whatever lens they want, so that minuscule slice of the legitimate requests is still served, albeit with a degraded experience.
This is an LLM response. It's the classic pattern where the LLM says something completely unrelated to the topic at hand, realizes that it doesn't have a backspace key, and tries to hedge it in.
Yes; and either yes or the author is separating walled social network gardens from "the internet". The "real internet", as you say, is not the addictive algorithmic feeds.
I believe that the "real internet" you're talking about is larger than it's ever been, but the signal-to-noise ratio of the whole internet has been killed by even larger amounts of noise. So it's difficult to find these smaller forums and get involved with them.