Programming

17374 readers

156 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

117

Announcing freenginx.org (freenginx.org)

submitted 8 months ago by canpolat@programming.dev to c/programming@programming.dev

11 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] mcherm@lemmy.world 28 points 8 months ago (3 children)

How concerned should I be?

What are the unspecified policies the developer claims that the company has failed to uphold? Who is this particular developer, and how much should I trust them? (I don't follow nginx development at all.)

I celebrate the fact that open source licenses exist specifically to allow people to make a fork like this when they have disagreements! But I don't know enough about this particular case to decide how it should affect my own plans.

[–] canpolat@programming.dev 17 points 8 months ago

Who is this particular developer

As far as I understand from the discussions about the topic, Maxim Dounin was one of the few core developers of nginx. Looks like Wikipedia has already been updated.

[–] Corngood@lemmy.ml 14 points 8 months ago (1 children)

http://freenginx.org/pipermail/nginx/2024-February/000007.html

The most recent "security advisory" was released despite the fact that the particular bug in the experimental HTTP/3 code is expected to be fixed as a normal bug as per the existing security policy, and all the developers, including me, agree on this.

And, while the particular action isn't exactly very bad, the approach in general is quite problematic.

I read something about this the other day, but I'm having trouble wrapping my head around it.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24989 https://my.f5.com/manage/s/article/K000138444 https://mailman.nginx.org/pipermail/nginx-announce/2024/NW6MNW34VZ6HDIHH5YFBIJYZJN7FGNAV.html

This seems to have the best discussion I've found:

https://news.ycombinator.com/item?id=39373612

[–] mcherm@lemmy.world 2 points 8 months ago

Thank you.