3 ms·
Their groundbreaking research was improvements that were directly derivative of work shipped with a license that said all derivative works must be provided unde
by michaelmrose 9y ago
Their groundbreaking research was improvements that were directly derivative of work shipped with a license that said all derivative works must be provided under the same free license they received the work with.
Your tone seems to suggest that some obligation exists that some obligation exists to do more than share the source to any improvements.
This obligation is wholly and totally imaginary. Its as if someone gave another party an entire farm and in the contract specified that he could eat some of the food that grew from it and that someone threw a fit when the first party walked up and made a sandwich.
Seeing as there is no sane and legal way to require anyone to pay for said patches the reasonable way to fund such an effort is to get the community to voluntarily fund such an effort with whatever platform is most useful preferably in advance.
It seems that they have instead chosen to rely on a mixture of manufactured drama, illegal threats, and general unpleasantness to keep their efforts from being well integrated with mainstream. While this remains so they can offer definable value.
In the long run I predict bankruptcy and irrelevance for a company that few care about now and none will care about later.
- hitekker 9y agoYeah, the parent's summary is tripe and implies that the GRSecurity is somehow faultless in the drama they've vehemently instigated time and time again. I'm having trouble seeing, apart from ignorance or misinformation, why anyone would condone GRSecurity. The code is helpful but you wouldn't want the authors in a position of authority over the operating system of a billion-plus computers. Right now, most arguments in defense of GRSecurity are simply: "Two sides are arguing, therefore they're both wrong. Aren't I smarter for pointing it out?"
- sighsagain 9y agoTheir research are in no way 'directly derivative' of the linux kernel. Their implementation was based on linux, but since then Microsoft and Apple have all adopted their RESEARCH of novel ways to eliminate entire CLASSES of bugs in their operating systems and as a result are far ahead of vanilla linux in this area. KSPP is a program started by some corporations (including Intel which is the parent company that was being talking about that messed with trademarks) and they pay some developers (such as kees cook) to rip off grsecurity/PaX code. It's funny how you talk about obligation when linus is here calling them clowns for their code which has for years protected systems which would otherwise be vulnerable such as vanilla linux kernels just because they are not in the format that the linux upstream wants? Doesn't hero worship get tiring? You make predictions about something you are seemingly ignorant about because they have customers because some people can't rely on the joke that is upstream linux security.
- eropple 9y agoThe killed comment on this thread has a line in it that's spectacular in its misunderstanding (or its dishonesty) that needs a brief explanation: > Their research are in no way 'directly derivative' of the linux kernel. Their implementation was based on linux This means that it's captured under the GPL, and anyone can do as they like pursuant to the license (which grsecurity has attempted, repeatedly, to constrain in contravention of that license), and that this guy has an a-gen-da and something to sell you.