2017-04-30 13:50 GMT+02:00 SK <yandere...@riseup.net>: > You can't really change license because it is a kernel patch so it has > to be GPLv2 from what i understand.
Really? Can you remind me when Grsecurity or PaX Team distributed the Linux kernel? If they did, all code is under GPL-2. But that never happened (if I'm right). You can't talk about any GPL violation because it has nothing to do - Linux kernel was not affected by a patch that never hit it! :) Funny, but true :) The second: you can't use grsecurity patch (even now!), because grsecurity is a registered trademark: """ Can I continue to use the name grsecurity? grsecurity® is a registered trademark by Open Source Security Inc. We will continue to use it in our official work. We ask that any community-based ports or additions to the last public official grsecurity patch not use the grsecurity trademark. Replacing the "grsec" uname addition, removing the grsecurity boot logo from the patch, and removing "grsec" from associated package names at minimum will make this easier and avoid confusion. All copyright and license notices must remain intact as required by the GPL. """ https://grsecurity.net/passing_the_baton_faq.php Alpine Linux changed the name 'grsec' to 'hardened', but that's not enough: you need to remove all references to 'grsecurity'. What does it mean? e.g.: # sysctl -a | grep grsecurity Exactly! In practice, this means you can't use grsecurity patch (or use the sed)! :) Daniel
