There have been arguments (e.g. by Bruce Perens [1]) that this kind of behavior violating the GPLv2 section which prohibits the addition of further restrictions to the license, when the grsecurity team started doing similar things with their Linux patches.
However this isn't really something that has been explored too far beyond that (at least to my knowledge). I'd personally tend towards this being more of a gap in the GPL's protections though, as forcing continued access to further updates would open a massive can of worms. Because then you'd need to figure out what is and what isn't a disallowed punishment for sharing GPL'd source code for any future contract between the two parties.[1] https://perens.com/2017/06/28/warning-grsecurity-potential-c...
No comments yet.