News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Wednesday November 18, 2026 @02:40PM (#50551055)
A more holistic risk-analysis would also need to consider the fact that a high-performance webserver written in Rust may also have memory safety issue due to use of "unsafe" features or unsafe dependencies, may be affected by memory safety issues in the standard library, may also have catastrophic logic errors, may be more affect by supply chain risks due to the use of a language-level package manager, and may have a larger patch gap.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ViewTrick1002 on Wednesday November 18, 2026 @02:46PM (#50551139)
Which is like complaining that Python is written in C.

Which is a far smaller surface as seen by research into incorporating rust in Android leading to none of the high profile vulnerabilities C and C++ led to previously.

Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Wednesday November 18, 2026 @02:49PM (#50551169)
By research you mean blog posts by Google?
Re:Pre-auth RCE in Nginx HTTP/2 handling by ViewTrick1002 on Wednesday November 18, 2026 @02:56PM (#50551279)
What specifically distinguishes the empirical research presented in Google’s blog post from your definition of research?

https://blog.google/security/rust-in-android-move-fast-fix-t...

Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Thursday November 19, 2026 @12:40AM (#50556450)
Research is not just making some plots and posting them on the internet. A proper scientific studies would need to be done much more carefully, if you want to get meaningful results, because there is a lot which can go wrong at any level. This is something learned people learned the hard way in empirical sciences. In particular, in this setting I do not see how one could ever properly control for confounding factors. Such a study should also be peer reviewed. Also if there are commercial interests mixed-up this needs to be questioned carefully.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ux266478 on Wednesday November 18, 2026 @03:44PM (#50551875)
Not in the slightest. It's like pointing out that a Python script calling out to binaries written in C doesn't have the memory safety of Python's GC. Which is obviously the case, and if you're a serious developer it's a failure point you're very mindful of.

On the Android point, I remember those metrics were highly flawed and didn't account for the inequality of substructural type ergonomics in different contexts. You can get very nice metrics by rewriting things that fit to the grain of safe Rust, which gives you an inaccurate picture of how much unsafe code is "real world". LLMs have changed the field here, but it's worth pointing out that blog post you're referencing was more self-congratulatory marketing than serious science.

Also problematically, I remember it being highly misleading in that the actual observed result was lower severity in vulnerabilities, but a very minimal effect on the total number over all. That's certainly significant, but it wasn't how it presented itself, which is rather problematic if you expect people to take it seriously.

Measurements probably real, but not worth citing.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @03:30PM (#50551719)
This argument is cope.

In theory, that could be possible. In practice, there have been many many case studies demonstrating the opposite.

e.g. Cloudflare replaced Nginx with Pingora: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...

> With those assurances we can focus more on how a change to our service will interact with other services or a customer's origin. We can develop features at a higher cadence and not be burdened by memory safety and hard to diagnose crashes.

> When crashes do occur an engineer needs to spend time to diagnose how it happened and what caused it. Since Pingora's inception we’ve served a few hundred trillion requests and have yet to crash due to our service code.

> In fact, Pingora crashes are so rare we usually find unrelated issues when we do encounter one. Recently we discovered a kernel bug soon after our service started crashing. We've also discovered hardware issues on a few machines, in the past ruling out rare memory bugs caused by our software even after significant debugging was nearly impossible.

The CVE counts for new parts of the Linux kernel written in Rust are much lower than the (recent) CVE counts for even mature, years old parts of the Linux kernel written in C, to say nothing of the historical record.

Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Thursday November 19, 2026 @01:10AM (#50556617)
There is basically no meaningful part of the kernel written in Rust from which one could conclude this. There is now binder, but this was only recently merged and I am not sure what data there is about it (and how it would compare to new C code written with a focus on memory safety).
Re:Pre-auth RCE in Nginx HTTP/2 handling by slopinthebag on Thursday November 19, 2026 @12:07AM (#50556279)
A more holistic risk-analysis would also need to consider the fact that wearing seatbelts in motor vehicles still leaves drivers vulnerable to drive-by shootings, may be affected by massive boulders crashing on top of the vehicle, driving off a bridge, or gas explosions, and costs more to produce.
Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Thursday November 19, 2026 @01:07AM (#50556594)
In my view, the Rust argument is more like that driving (in C) can not possible be safe because there is always the inherent risk of steering into an obstacle, so we have to abandon it completely and only use trains (which entirely eliminate this class of steering errors). But this is argument made in the 1950s without considering that seatbelts and other modern techniques, driver tests, speed limits can make driving a lot safer (as seen today when compared to the 1950s).