this post was submitted on 17 May 2024
44 points (89.3% liked)

Linux

48323 readers
620 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
you are viewing a single comment's thread
view the rest of the comments
[–] CosmicCleric@lemmy.world 8 points 6 months ago* (last edited 6 months ago) (1 children)

and the kernel folks just went “it is the kernel, everything is critical”

tl;dr: this is pretty much an elaborate “go fuck yourself” towards shady ‘security’ companies.

Apologies for my ignorance, but could you elaborate?

I'm sincerely not seeing the connection between saying everything is critical as a go fuck yourself towards those companies.

Is it a 'death by quantity' thing?

~Anti~ ~Commercial-AI~ ~license~ ~(CC~ ~BY-NC-SA~ ~4.0)~

[–] aard@kyu.de 30 points 6 months ago (1 children)

Is it a ‘death by quantity’ thing?

Pretty much that - those companies rely on open projects to sort it for them, so they're pretty much scraping open databases, and selling good data they pull from there. That's why they were complaining about the kernel stuff - the info required was there already, just you needed to put effort in, so they were asking for CVEs. Now they got their CVEs - but to profit from it they'd still need to put the same effort in as they'd had to without CVEs in place.

[–] taladar@sh.itjust.works 14 points 6 months ago* (last edited 6 months ago)

the info required was there already, just you needed to put effort in

Not really. This is mostly what this is all about. The companies are insisting that open source projects should do analysis of security impacts in addition to fixing the bugs whenever some "security researcher" runs some low effort fuzzing or static analysis thing that produces large numbers of bug reports and assigns CVEs to them without the consent of the project. The problem is that such an impact analysis is significant effort (often orders of magnitude more than the fix itself) by people with deep knowledge about the code bases and only really useful to the customers of those companies who want to selectively update instead of just applying all the latest fixes.