this post was submitted on 15 Feb 2024
340 points (97.8% liked)

Linux

48356 readers
674 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
340
announcing freenginx.org (mailman.nginx.org)
submitted 9 months ago by exception4289@lemmy.world to c/linux@lemmy.ml
50 comments fedilink hide all child comments
 

Maxim Dounin announces the freenginx project.

As such, starting from today, I will no longer participate in nginx development as run by F5. Instead, I’m starting an alternative project, which is going to be run by developers, and not corporate entities:

you are viewing a single comment's thread
view the rest of the comments
[–] fmstrat@lemmy.nowsci.com 60 points 9 months ago* (last edited 9 months ago) (3 children)

TLDR; F5 owns Nginx. Making corporate over security decisions. New community fork from one of the core devs at http://freenginx.org/. Too new to know if it will be adopted by other mainstream projects that currently leverage/embed nginx.

Note: If you use nginx and are concerned about security, consider a look at projects such as owasp/modsecurity-crs which include security layers on top of nginx.

[–] xinayder@infosec.pub 49 points 9 months ago (2 children)

That doesn't seem to be the case. From what I read on HN, the dev quit because he thought it didn't make sense to submit CVEs for temporary/wip solutions, and F5 thought otherwise.

So as I see it, the developer quit because he didn't agree that a CVE should be opened for a work-in-progress solution that was live on Nginx.

[–] acockworkorange@mander.xyz 37 points 9 months ago

So basically just drama?

[–] exception4289@lemmy.world 18 points 9 months ago

That's what I read, too.
It gives a new perspective on the subject.

Sad to see the workforce being split up, though.

[–] MangoPenguin@lemmy.blahaj.zone 25 points 9 months ago (2 children)

Making corporate over security decisions.

I read the opposite essentially, that F5 is publishing CVEs and the dev did not want them to.

[–] towerful@programming.dev 14 points 9 months ago (1 children)

Yeh, seems like the CVEs were against an alpha branch.
So, perhaps its a good reminder not to use alpha in production... But I feel it warranted a bug report instead of a "Common Vulnerabilities and Exploits" notice, normally something used to notify potentially production deployed systems of an issue.

That would be like Pepsi issuing a product recall to all retail outlers for a product that has only been tested internally (kinda)

[–] Kushan@lemmy.world 11 points 9 months ago (1 children)

I think it's more like pepsi issuing a product recall for something that has been accidentally left on the side of the road. You know you should not be drinking it anyway, but you also know someone would try it.

[–] Bene7rddso@feddit.de 3 points 9 months ago

It was on purpose on the side of the road so people could gice feedback. But the issue wasn't a health issue (privilege escalation, etc), it just wasn't tasty (DoS). Something you really don't want to sell in the store, but in an alpha/beta version it's no big deal

[–] BaumGeist@lemmy.ml 1 points 9 months ago

I'll justbuse this excuse to repost my thoughts from the other threas https://lemmy.ml/comment/8358568