Just to reiterate, I don’t think RH is in the right here.
They’re “punishing” you by not taking any more of your money for future versions. Maybe we’ll see a court case out of it to settle the question but I doubt it. But consider you are a customer, and you have to ship RH binaries with your application. In order to comply with the license you must also make the source available. RedHat can’t stop you from doing so, they just won’t give you access to any more updates (and stop taking your money). So now you can’t ship security updates to your customer. So now you have a legal liability by being a RedHat customer. Either you fail to comply with GPL yourself for the sake of updates, or you expose your customer to known security risks because you compiled with the GPL. So … why do business with RedHat anymore? Explain this problem to your customers why you can’t certify on RedHat anymore.
“If you distribute the code you’re entitled to distribute we can terminate your contract” is identical to “if you distribute the code you’re entitled to distribute we can charge you money”. They’re additional restrictions that are unconditionally not under any circumstances allowed by the GPL. You cannot restrict redistribution in any way for any reason outside of the GPL terms.
The second you do so, you are no longer covered under the GPL and everything you’re distributing is copyright infringement.
“If you distribute the code you’re entitled to distribute we can terminate your contract” is identical to “if you distribute the code you’re entitled to distribute we can charge you money”
I’m not a lawyer, but I categorically disagree that those two statements are the same. If someone takes RedHat to court and wins, fantastic. But as I’ve said, I wouldn’t make business plans that rely on winning that case.
Just to reiterate, I don’t think RH is in the right here.
They’re “punishing” you by not taking any more of your money for future versions. Maybe we’ll see a court case out of it to settle the question but I doubt it. But consider you are a customer, and you have to ship RH binaries with your application. In order to comply with the license you must also make the source available. RedHat can’t stop you from doing so, they just won’t give you access to any more updates (and stop taking your money). So now you can’t ship security updates to your customer. So now you have a legal liability by being a RedHat customer. Either you fail to comply with GPL yourself for the sake of updates, or you expose your customer to known security risks because you compiled with the GPL. So … why do business with RedHat anymore? Explain this problem to your customers why you can’t certify on RedHat anymore.
“If you distribute the code you’re entitled to distribute we can terminate your contract” is identical to “if you distribute the code you’re entitled to distribute we can charge you money”. They’re additional restrictions that are unconditionally not under any circumstances allowed by the GPL. You cannot restrict redistribution in any way for any reason outside of the GPL terms.
The second you do so, you are no longer covered under the GPL and everything you’re distributing is copyright infringement.
I’m not a lawyer, but I categorically disagree that those two statements are the same. If someone takes RedHat to court and wins, fantastic. But as I’ve said, I wouldn’t make business plans that rely on winning that case.