PaX / Grsecurity enforced memory safety via kernel edits on all programs including C programs 26 years ago. More than a quarter century ago this problem was solved. Then in 2017 or 2019 or so they decided to violate the Linux and GCC copyrights by adding a “no redistribution” clause (and a choice of venue clause too) that runs counter to the ban on additional terms in the copyright license memorandum of Linux and GCC (gpl). Bruce Perens then noted this copyright violation and then Grsecurity (Open Source Security) sued him for libel and then lost and had to pay Bruce’s court and attorneys fees. Grsecurity argued in front of the appellate court that adding this clause is not a copyright violation: the judges just seemed to shake their heads in the video not buying it. However the issue was libel and not federal copyright. Linux had previously entered the security biz with nsa Linux: thus the fair use exception in the more recent Oracle/Google Supreme Court case does not necessarily help Grsecurity. Linus refuses to sue and anyone that asks on the lkml is censored and banned. There are auto spam filters to prevent all discussion. RMS also refuses to do anything. Programmers believe that a patch doesn’t have to obey the copyright of the parent work and constantly claim that if you just distribute a diff file you can do as you please. They ban you if you point out that a diff is an annotation and is a derivative work and the US Copyright office says the original copyright owner has the right to control derivative works. They then call you a myspginist when you point this out and say you’re insane and will never be a lawyer etc.