340
announcing freenginx.org
(mailman.nginx.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Feb 2024
340 points (97.8% liked)
Linux
48138 readers
456 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
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-crswhich include security layers on top of nginx.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.
So basically just drama?
That's what I read, too.
It gives a new perspective on the subject.
Sad to see the workforce being split up, though.
I read the opposite essentially, that F5 is publishing CVEs and the dev did not want them to.
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)
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.
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
I'll justbuse this excuse to repost my thoughts from the other threas https://lemmy.ml/comment/8358568
I will never understand how they became so massive.
I could say the same about Microsoft.