3 ms·
> It's not a single organization calling the shots where they can have a meeting behind closed doors about the vulnerability and internally incubate a patchset.
by masklinn 9y ago
> It's not a single organization calling the shots where they can have a meeting behind closed doors about the vulnerability and internally incubate a patchset. That's simply not how Linux development works.
Bullshit. Ultimately, Linus decides what does or does not go in, assisted by the subsystem maintainers he picked. If they wanted to have closed doors meeting, they could, and would.
FreeBSD and the like have no more and no less "single organisation calling the shots", the only difference is that they're not a human clusterfuck.
> It might not be ideal from a security person's perspective but from everyone else's perspective this model has been the driving factor behind the most successful collaborative project of all time.
That just means Linux at large will ultimately get ignored for anything security-sensitive, and only specific distributions will be contacted.
- Sir_Cmpwn 9y agohttps://en.wikipedia.org/wiki/FreeBSD#Development https://en.wikipedia.org/wiki/FreeBSD#Development
- masklinn 9y agoYeah so? > The FreeBSD Project is run by around 500 committers, or developers who have commit access to the master source code repositories and can develop, debug or enhance any part of the system. I doubt there are 500 people with push access to the main Linux repository. Again, the FreeBSD folks just have their shit together.
- Sir_Cmpwn 9y agoI was pointing out the existence of a governing body and a core team on FreeBSD, for which there is no analogue on Linux. There is no "the main Linux repository".
- masklinn 9y ago> there is no analogue on Linux. There is no "the main Linux repository". Of course there is. Linus decides what goes into the mainline kernel, his repository is literally called "Linux kernel source tree"[0], with the stable "archive" being sensibly called "Linux kernel stable tree"[1], and Linux's analogue to the freebsd core team is de-facto Linus and his trusted maintainers, the people from whom he reviews and pulls commits. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/about/ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin... [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux...
- Sir_Cmpwn 9y agoYou don't understand. This is a list of people who have ownership over some part of Linux: https://github.com/torvalds/linux/blob/master/MAINTAINERS https://github.com/torvalds/linux/blob/master/MAINTAINERS Linus might have the "final say" but all of the work and knowledge is encapsulated in these people and they are generally given the autonomy to organize and maintain their subsystems as they see fit. As for Linus's tree, it's probably the most Linux Linux that's out there, but it's hardly the only one. Hardly anyone actually runs Linux from Linus's tree. Most distros maintain their own trees with their own patchsets.
- masklinn 9y ago> You don't understand I perfectly understand that you're trying to excuse the utter clusterfuck that is the linux project's handling of security notifications, apparently on the grounds that they don't have their shit together and refuse to do so, ever. > Most distros maintain their own trees with their own patchsets. Yeah, and they can actually be trusted to not break embargoes.
- johnbellone 9y agoYes, at a macro level that is how it works, but practically due to having an enormous number of distributions there are many more forks. For example, the CentOS distribution maintains their kernel[0] separately from RHEL. [0]: https://git.centos.org/summary/?r=rpms/kernel.git https://git.centos.org/summary/?r=rpms/kernel.git