News for hackers. Stuff that matters.
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.