Forget about future vers; it's a distraction. If they said "if you exercise your rights under GPL, we'll kill a kitten" it'd infringe too.
-
-
Replying to @RichFelker
They aren't saying that, it's an assumption we're making: if a company published it, they likely wouldn't continue to do business with them.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
As soon as that happens, or as soon as they in any way suggest that that might happen, there's grounds for litigation.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
By Linux kernel developers, not the customer. There are no grounds for one of their customers to sue since it's not their software license.
1 reply 0 retweets 1 like -
Replying to @CopperheadOS @RichFelker
Linux kernel industry standards and cultural norms are not the place to look if you're expecting such strong GPL enforcement...
2 replies 0 retweets 4 likes -
Replying to @CopperheadOS
Kernel developers are lax over inconsequential infringements like missing changelogs, wrong way of conveying src, unmodified use, etc...
2 replies 0 retweets 0 likes -
Replying to @RichFelker
No one has sued NVIDIA and other companies producing binary drivers for infringement, even Linux-only ones that are clearly derivatives.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
And grsecurity is not even that. It's not a binary. It's a patch, distributed to customer and applied to kernel sources for their builds.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Can source code even be considered to infringe upon the GPL until it's actually built, linked or run? In that case customer is violating it.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Linux kernel developers would need to sue grsecurity customers building and using infringing kernels, not even grsecurity itself.
1 reply 0 retweets 0 likes
If grsec is leading their customers to believe they can't safely exercise their rights under GPL, then grsec is infringing.
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.