News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by gmueckl on Wednesday November 18, 2026 @02:52PM (#50551225)
rust isn't invulnerable.
Re:Pre-auth RCE in Nginx HTTP/2 handling by sophacles on Wednesday November 18, 2026 @03:38PM (#50551827)
A tank isn't invulnerable either, but of someone starts shooting at me I'd rather be in a tank than on a 50 year old bicycle.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hunterpayne on Wednesday November 18, 2026 @06:09PM (#50553666)
Fun fact, Russian soldiers ride on top of their tanks and APCs because its safer than being inside of one during an assault. Doesn't mean you are wrong, but there will always be trade-offs. There is no such thing as perfectly secure.
Re:Pre-auth RCE in Nginx HTTP/2 handling by openasocket on Wednesday November 18, 2026 @07:09PM (#50554189)
Tank desant is practiced because there isn’t room in the tank to fit extra people. It’s very much not safer outside of a tank than inside! It’s actually the worst of both worlds, because you don’t have the armor protection but are highly visible. The only advantage it gives over infantry assault on foot is mobility. Which is why it’s generally only practiced when there aren’t sufficient APCs/IFVs available
Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @09:56PM (#50555488)
Not exactly true. BMPs are death traps, sure, and sitting on top of those instead of in them is rational given the risk of burning to death inside of one or being obliterated by a mine.

But the only reason to sit outside a tank rather than in one is because riding on a vehicle is safer than walking through an open field. Tank crews are not sitting outside of their tanks, and they don't have seats inside for passengers.

Re:Pre-auth RCE in Nginx HTTP/2 handling by hunterpayne on Wednesday November 18, 2026 @06:07PM (#50553653)
Fun fact, these specific types of problems aren't possible on a JVM. Yet somehow Java isn't the right language to write a webserver in. These problems are possible in Rust and C/C++. At least its "hard" to have this type of problem in Rust.

Security is hard and is mostly about the number of engineers and amount of time spent looking at a specific implementation. When writing code, do you think about the problems of leaking information due to different operations taking specific amounts of time? That's an actual concern when writing a prod service that uses the network. And it has to be balanced against scalability and issues caused by DOSes. It isn't trivial and it isn't binary...there are always trade-offs. Nothing will ever be perfectly secure and usable and scalable.