News for hackers. Stuff that matters.
Re:Ruby2ßhell: Pre-authentication RCE on stock Rails by nsagent on Thursday November 19, 2026 @08:45AM (#50560032)
Do you use core abstractions like Vec, String, Box, Arc, and Mutex? If so, those are built using unsafe code internally.
Re:Ruby2ßhell: Pre-authentication RCE on stock Rails by tialaramex on Thursday November 19, 2026 @09:06AM (#50560294)
Lets compare what's inside this Ruby bug, a C function rb_str_casemap which is 40-50 lines of C fiddling with pointers and calling into macros that presumably are familiar to Ruby developers but opaque to an outside viewer. Is it fixed? I guess so but I can't see very well to be sure, it was counting stuff before and now it is being more careful, I hope it's correct this time.

... against str::to_lowercase the Rust function which has a single line of unsafe code, with a two line rationale provided to explain why it's OK to do this. As a subject matter expert I agree with the rationale. LGTM.

Re:Ruby2ßhell: Pre-authentication RCE on stock Rails by nsagent on Thursday November 19, 2026 @11:46AM (#50562512)
This sub-thread in the conversation is about Java, so comparisons to Ruby aren't what's relevant. Here's part of the relevant GP comment.

> It's important to note that Java, like Rust, is generally seen as a memory safe language. But it has bits of assembly, just like Rust has unsafe blocks, to handle some operations.

And according to sources like CISA and the NSA [1], Java is considered memory safe. Furthermore, Rust has been found to have some memory safety issues as well [2]. I think the point to get across is that yes, Rust can help eliminate a very large set of memory safety bugs, but it's prone to issues that other generally considered memory safe languages also have: at some point to do useful work there are going to be unsafe operations. The surface area might be much smaller, so you're likely better off using a memory safe language if you can help it, but it's not a panacea for having layers of security, especially since it means any issue found is likely to affect a large swath of code written in the language because it's in a load bearing area of the language ecosystem.

[1]: https://www.nsa.gov/Press-Room/Press-Releases-Statements/Pre...

[2]: https://www.microsoft.com/en-us/security/blog/2026/11/09/for...

Re:Ruby2ßhell: Pre-authentication RCE on stock Rails by tialaramex on Thursday November 19, 2026 @12:21PM (#50562993)
Java's String::toUpperCase appears to be quite a lot more complicated than the Rust but it is at least all Java and thus without careful inspection I can assume it's memory safe.
Re:Ruby2ßhell: Pre-authentication RCE on stock Rails by teaearlgraycold on Thursday November 19, 2026 @01:30PM (#50564080)
Unsafe rust is still safer than normal C.
Re:Ruby2ßhell: Pre-authentication RCE on stock Rails by jerf on Thursday November 19, 2026 @01:50PM (#50564412)
Do you run on CPUs based on the von Neumann architecture?

If so, those are built on unsafe operations internally.

Safety is a lot more complicated than "whether it is in an unsafe block of code in Rust". If you insist that an unsafe primitive can not be handled well enough to become "safe" by some definition of safe then you collapse the entire programming language hierarchy into "everything is completely unsafe". Which may, from a certain point of view, be true, but isn't a particularly useful classification scheme.

Re:Ruby2ßhell: Pre-authentication RCE on stock Rails by afdbcreid on Thursday November 19, 2026 @03:44PM (#50566098)
Arrays in Java (a loose equivalent of `Vec`) is a runtime primitive and implemented in a memory-unsafe language. References (loose equivalent of `Box` and `Arc`) as well. Java's `synchronized` (a loose equivalent to `Mutex`) as well. Those are not good counterexamples.