News for hackers. Stuff that matters.

stuxf

Re:Ruby2ßhell: Pre-authentication RCE on stock Rails on Thursday November 19, 2026 @04:36AM (#50557936)
would you rather we publish a PoC for a vulnerability that doesn't even have a patch yet? e.g self-hosted GitLab still hasn't shipped a newer version of Ruby that's patched...

would be wildly irresponsible

Re:Ruby2ßhell: Pre-authentication RCE on stock Rails on Thursday November 19, 2026 @03:42AM (#50557565)
this relies on specific behavior with how the upcase function worked, the ß is the only one that expands in a way that works for this vulnerability.
Re:Ruby2ßhell: Pre-authentication RCE on stock Rails on Thursday November 19, 2026 @03:23AM (#50557417)
we were thinking of naming it ruby off rails haha, but this title ties into how this vulnerability works which was super cool
Re:Judge a book by its first pages on Saturday July 18, 2026 @07:54PM (#48963643)
exactly my thoughts too, this is a great way to digitally recreate the bookstore experience :)
Re:1k Words: A Writing Contest on Monday July 06, 2026 @02:37PM (#48808686)
Been looking to write more, this looks great! I love the general premise of just converting picture => 1000 words.
Re:Hardening Firefox with Anthropic's Red Team on Friday March 06, 2026 @07:47AM (#47274310)
Makes sense, thank you!
Re:Hardening Firefox with Anthropic's Red Team on Friday March 06, 2026 @07:39AM (#47274253)
It's interesting that they counted these as security vulnerabilities (from the linked Anthropic article)

> “Crude” is an important caveat here. The exploits Claude wrote only worked on our testing environment, which intentionally removed some of the security features found in modern browsers. This includes, most importantly, the sandbox, the purpose of which is to reduce the impact of these types of vulnerabilities. Thus, Firefox’s “defense in depth” would have been effective at mitigating these particular exploits.

Re:The path to ubiquitous AI (17k tokens/sec) on Friday February 20, 2026 @06:35AM (#47086706)
I totally buy the thesis on specialization here, I think it makes total sense.

Asides from the obvious concern that this is a tiny 8B model, I'm also a bit skeptical of the power draw. 2.4 kW feels a little bit high, but someone else should try doing the napkin math compared to the total throughput to power ratio on the H200 and other chips.

Re:Show HN: Echo, an iOS SSH+mosh client built on Ghostty on Wednesday February 18, 2026 @02:52PM (#47065476)
finally I can move off termius, this looks great!
Re:Expensively Quadratic: The LLM Agent Cost Curve on Monday February 16, 2026 @02:42AM (#47032078)
> Some coding agents (Shelley included!) refuse to return a large tool output back to the agent after some threshold. This is a mistake: it's going to read the whole file, and it may as well do it in one call rather than five.

disagree with this: IMO the primary reason that these still need to exist is for when the agent messes up (e.g reads a file that is too large like a bundle file), or when you run a grep command in a large codebase and end up hitting way too many files, overloading context.

Otherwise lots of interesting stuff in this article! Having a precise calculator was very useful for the idea of how many things we should be putting into an agent loop to get a cost optimum (and not just a performance optimum) for our tasks, which is something that's been pretty underserved.

Re:AI Slop vs. OSS Security on Thursday November 06, 2025 @12:01PM (#45837385)
I agree with a lot of things said in this article, I also think some sort of centralized trust system for OSS bug bounty would be a really good solution to this problem

> The downside is that it makes it harder for new researchers to enter the field, and it risks creating an insider club.

I also think this concern can be largely mitigated or reduced to a nonissue. New researchers would have a trust score of zero for example, but people who consistently submit AI slop will have a very low score and can be filtered out fairly easily.