Earlier quoted context omitted.
I thought the same thing. The Linux kernel has been "freely available" for a measly 26 years, and will continue to be so.
Why are the grsecurity patches not included in the Vanilla Kernel? https://unix.stackexchange.com/questions/59020/why-are-the-g...
Passing the Baton
21–30 of 82 posts
Re: Passing the Baton
#22It may end up being the best thing that could have happened for kernel security in the end.
[1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Pr...
Re: Passing the Baton
#23I love how grsecurity is always quick to point out how generous they have been by providing the patches for free. > We have been providing grsecurity freely for 16 years. Meanwhile the kernel upon which their work is built has been provided for free for much longer, and continues to be.
The technologies these dudes developed are used in the vast majority of OSs outthere.
Instead of posting a cynical comment here you should thank them.
Re: Passing the Baton
#24I love how grsecurity is always quick to point out how generous they have been by providing the patches for free. > We have been providing grsecurity freely for 16 years. Meanwhile the kernel upon which their work is built has been provided for free for much longer, and continues to be.
It's not just the patches they provided for, it's also innovation. The technologies these dudes developed are used in the vast majority of OSs outthere. Instead of posting a cynical comment here you should thank them.
Re: Passing the Baton
#25Earlier quoted context omitted.
It's not just the patches they provided for, it's also innovation. The technologies these dudes developed are used in the vast majority of OSs outthere. Instead of posting a cynical comment here you should thank them.
I mean, the grsecurity guys aren't the PAX guys.
Re: Passing the Baton
#26Earlier quoted context omitted.
Torvalds claims [0] that he did not do enough arguing with upstream: > The apparent inability (and perhaps more importantly - total unwilling[n]ess) from the PaX team to be able to see what makes sense in a long-term general kernel and what does not, and split things up and try to push the sensible things up (and know which things are too ugly or too specialized to make sense), caused many PaX features to never be me…
PaX is developed independently from and usually shipped with grsec patches. AFAICT Spengler's not directly involved, and Torvald's comments don't reflect on them.
Re: Passing the Baton
#27Re: Passing the Baton
#28Re: Passing the Baton
#29How does this work at a licensing level? GRSecurity are patches to the Linux kernel right? Can you distribute patches for a GPL licensed software without the patches themselves being GPL?
The way these things tend to work is "It's GPL, but if you redistribute it publicly we terminate your subscription with no refund." (I think RHEL binaries work the same way, for instance.) The reason for companies to pay is to get reliable updates for new versions, so that they can avoid hiring a bunch of people in-house to build / forward-port things. So usually this incentive works.
Now that grsec is completely unavailable without a paid subscription, either source or binary, it'd be interesting to see if the incentive holds up, or whether someone wants to burn a subscription to get a version out to the public. I imagine that they're cautious about who they allow to sign up as a customer.