Non-technical merits like those are actually critically important to acceptance of a free software project. They can make or break it.
-
-
Sure, but let's not go off topic. The topic was "KSPP making Grsec/PaX irrelevant".I take that you agree these are not competing technically
1 reply 0 retweets 2 likes -
My point is that being upstreamed is as much a technical achievement as coming up with the mitigations in the first place.
2 replies 0 retweets 0 likes -
Then your point is fairly questionable
1 reply 0 retweets 0 likes -
Well,
@paxteam himself claims the upstreaming effort would be a vast undertaking, so...2 replies 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
So, you seem to undermine the complexity of writing good mitigations. And for how long they have been available along with the source code
1 reply 0 retweets 0 likes -
Replying to @lazytyped @_pablosole_ and
They've been available in monolithic, history-free patch form and their authors have repeatedly mocked any attempts at upstreaming them.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
This is vastly false, you see what you want to see. Check the KSPP archives for how much the PaX Team has helped there
1 reply 0 retweets 2 likes -
Replying to @lazytyped @_pablosole_ and
Feel free to link to those; I just keep seeing comments like this: https://lwn.net/Articles/699314/ …
1 reply 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
You also have to consider that their failure to work with other people severely undermines some of their code.
2 replies 0 retweets 0 likes
E.g. PaX SIZE_OVERFLOW is total garbage due to limitations of GCC, but instead of working with GCC they'd rather have a crashy kernel.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.