News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @01:56PM (#50550500)
This is the reason why the oss project i work for is not publishing commits anymore outside of releases but people are freaking out over this.

Cant win.

Seriously reconsidering if open source has a future nowadays

Re:Pre-auth RCE in Nginx HTTP/2 handling by Aperocky on Wednesday November 18, 2026 @02:04PM (#50550593)
I mean, win or not, it has nothing to do with some people freaking out, and that certainly have nothing to do with whether open source have a future.
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @03:45PM (#50551899)
Not really sure what you’re trying to say; my main point is that OSS is going to change drastically in the next couple years
Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:23PM (#50550814)
> Seriously reconsidering if open source has a future nowadays

*In C or C++.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pjmlp on Wednesday November 18, 2026 @02:42PM (#50551099)
Until we don't replace UNIX clones, Khronos APIs, LLVM or GCC with something else.

C and C++ will stay around for a very long time, even with AI powered systems.

If anything, maybe that is a call that even if implementing compiler backends is hard and time consuming, bootstraping compilers, and new approaches to OS design, are the only path away from such dependencies.

Re:Pre-auth RCE in Nginx HTTP/2 handling by anthk on Wednesday November 18, 2026 @04:31PM (#50552398)
Rust is on its way. Vulkan is no GL, and Gallium it's something else over classical MESA under SGI/Sun.

Legacy 32 bit users with NetBSD and Hyperbola can survive a little with Go based tools/small browsers/mail/usenet/IRC clients and some web browsers with Bubblewrap, but not forever.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pjmlp on Wednesday November 18, 2026 @05:21PM (#50553108)
Rust being here matters,

https://www.khronos.org

https://vulkan.org/events/vulkanised-2027#program

The only thing closer to it is WSGL.

Also there are much more operating systems than those examples.

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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by perlgeek on Wednesday November 18, 2026 @02:29PM (#50550899)
So what happens when somebody tries to contribute based on the last-published commit? Do you merge/rebase their contributions for them?
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @03:44PM (#50551881)
Haven’t figured out how to deal with contributions going forward…

The issue is that we get dozens of PRs, generating a bunch of code is trivial but reviewing and merging it and making sure it doesn’t break in interesting ways is still pretty hard.

Personally I lean towards not accepting code contributions anymore, but accepting design documents for features and l bug reports etc

Re:Pre-auth RCE in Nginx HTTP/2 handling by mort96 on Wednesday November 18, 2026 @04:08PM (#50552137)
How about a strict anti LLM use policy for contributors? It adds what's basically a "proof of human work" challenge to opening new PRs, and effort required to review human PRs usually roughly scales in proportion to the amount of effort required to make human PRs. And human contributors who take time to make a PR manually are probably more likely to become longer term community members and not just drive-by contributors

It's not a perfect solution of course, it just takes OSS back to the fairly broken state it was pre-AI. Still, it might be an improvement and should be at least considered.

Re:Pre-auth RCE in Nginx HTTP/2 handling by baq on Wednesday November 18, 2026 @04:17PM (#50552238)
Amounts to ‘won’t be getting contributions‘ which is maybe not that bad at this point on the timeline
Re:Pre-auth RCE in Nginx HTTP/2 handling by mort96 on Wednesday November 18, 2026 @04:26PM (#50552328)
There's plenty of people who contribute to non-AI open source projects, you just don't get the lazy people who don't want to be a serious part of the project or the people who don't know how to program anymore
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @08:50PM (#50555086)
We do have a LLM disclosure policy.

I’m not sure how we could enforce an 0 LLM policy in practice though…

Re:Pre-auth RCE in Nginx HTTP/2 handling by seba_dos1 on Wednesday November 18, 2026 @10:26PM (#50555696)
You only need to enforce it enough to fulfill its goals.

https://xkcd.com/810/

Re:Pre-auth RCE in Nginx HTTP/2 handling by cluckindan on Wednesday November 18, 2026 @04:58PM (#50552776)
The future is in closed source ecosystems on a modified Harvard architecture
Re:Pre-auth RCE in Nginx HTTP/2 handling by davidkwast on Wednesday November 18, 2026 @07:16PM (#50554251)
WTF but I get the point
Re:Pre-auth RCE in Nginx HTTP/2 handling by kbolino on Wednesday November 18, 2026 @08:12PM (#50554753)
The actual behavior of a running system is extremely data-dependent. There is no security-relevant distinction between Harvard and modern von Neumann architectures anymore, and it's arguable that there ever was one in the first place.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jamesfinlayson on Wednesday November 18, 2026 @09:15PM (#50555229)
I'm sure things will stabilise in the near future.

That said, I just moved from a Linux based job to a Windows based job and it's been nice not having to be panicked about having update most of the technologies that my last job used. As an aside I did try in the past to make sure we were always updating dependencies but my manager was bothered by the amount of work that created. I'm watching that team now take forever to deal with these issues because they're too far behind to just version number and rebuild.