1) It's multiple years behind in terms of sec features 2) Grsec became unmergeable by Linus unwillingness to care about sec many years ago
-
-
Replying to @_pablosole_ @marcan42 and
3) saying grsecurity is illegal is just gross misunderstanding of licensing, literally fake news...
1 reply 1 retweet 1 like -
grsecurity's RAP includes a GPLv2-only compiler plugin (uses headers) for GPLv3-only GCC. QED.
2 replies 0 retweets 0 likes -
https://grsecurity.net/rap_faq.php . Last section. QED my ass.
1 reply 0 retweets 0 likes -
Yes, that is
@paxteam's hilarious licensing hack. It's wrong. The libgcc exception has *nothing* to do with GCC's license.1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
GCC is GPLv3, period, and the plugin system uses direct calls, and thus plugins are derived works, and thus they have to be GPLv3.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
What they claim *only* works if you use a GPLv3 shim to serialize compilation data into a non-linking format then operate on that.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
They do NOT do that, they wrote a simple plugin, which has to be GPLv3 because it DIRECTLY links into and calls GPLv3'd GCC.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
Nevermind the fact that there are many Linux arch ports that DO link libgcc, so they're wrong (or lying) about that too.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
The whole thing is an incorrect (either by negligence or malice) wank to try to attempt to restrict usage of RAP outside the kernel.
1 reply 0 retweets 0 likes
It's basically trying to abuse the FSF's "no proprietary GCC plugins" rules but it gets it completely wrong.
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.