News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tkz1312 on Wednesday November 18, 2026 @02:36PM (#50551009)
I now run all my network facing C code via fil-c. I have limited needs (ssh, static file server), but for those it works very well. I personally am more in favour of making existing battle tested C safer via fil-c or formal verification, than I am of rewriting the world in rust.

New code means new bugs, and losing the many years of accumulated bug fixes and hardening present in many critical pieces of our infra by rewriting in rust is not a desirable tradeoff. The new world we live in where fv has become many orders of magnitude cheaper also makes rust seem much less attractive.

Re:Pre-auth RCE in Nginx HTTP/2 handling by tgma on Wednesday November 18, 2026 @02:38PM (#50551027)
Fil-C is also a great solution, albeit with different performance trade-offs.
Re:Pre-auth RCE in Nginx HTTP/2 handling by safercplusplus on Wednesday November 18, 2026 @03:46PM (#50551908)
In theory, scpptool provides another solution with different performance, compatibility and portability trade-offs. Unlike Fil-C, it is not "fanatically compatible" with existing C code. But in theory, with maybe some minor adjustments to the code (and maybe less-minor adjustments to the build system), you can auto-translate your existing C code base to an essentially memory-safe subset of C++ at build-time [1].

While generally more of a hassle than Fil-C, the scpptool approach provides an incremental path to optimal performance (for performance-sensitive sections of the code) via migration to a (statically-enforced) memory-safe subset of C++. And unlike Fil-C, the scpptool solution essentially maintains the portability of the original code, as well as its deterministic performance and resource usage (i.e. no GC). It also supports ABI compatibility via "unsafe"/"check-suppression" annotations. The scpptool approach is not so much an alternative to Fil-C, as it is an optional path forward for C (or C++) code bases that may (or may not) be already using Fil-C for memory safety.

[1] https://github.com/duneroadrunner/SaferCPlusPlus-AutoTransla...

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:50PM (#50553482)
What good is a car that goes 1000 miles per hour if it has no brakes?

It's time for performance above everything else to die, especially on anything and everything that gets anywhere close to untrusted data.

Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @09:52PM (#50555461)
In many cases the performance is not that important, for example, SSH is often used to transmit mere kilobytes of text per second and I would prefer a safe SSH to a faster unsafe SSH. Or take mDNS, it servers several requests per minute max.
Re:Pre-auth RCE in Nginx HTTP/2 handling by gspr on Wednesday November 18, 2026 @02:58PM (#50551300)
This sounds like a fantastic solution, especially for non-high-volume stuff. Would you consider writing down your setup and experiences? I'm sure it'll be a hit on this site!
Re:Pre-auth RCE in Nginx HTTP/2 handling by jazzyjackson on Wednesday November 18, 2026 @03:23PM (#50551638)
fv?
Re:Pre-auth RCE in Nginx HTTP/2 handling by whilenot-dev on Wednesday November 18, 2026 @03:29PM (#50551706)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by andrepd on Wednesday November 18, 2026 @03:30PM (#50551729)
Formal verification.
Re:Pre-auth RCE in Nginx HTTP/2 handling by remixer-dec on Wednesday November 18, 2026 @05:42PM (#50553391)
Same, made a fil-c fork of nginx a while back, saved me from many RCEs https://github.com/remixer-dec/filc-nginx Don't have the tokens to maintain it though :(