No, it does not say this. It says that if someone gets a piece of software, a binary for example, they must be given the source code it was built upon on request. It does not say that they have to receive all future source code updates even if they don't get future versions of the software.
Yes, if the consequence of excercising freedom is death(or imprisonment) then you aren't actually free, because killing (or imprisonment) stops you from excercising freedom. Red Hat terminating your license does not stop you from excercising the freedom the GPL gives you.
Anyway, Red Hat's EULA doesn't restrict freedom 4. You asserted an alternative formulation where it does infringe to be equivalent.
I reject that equivalence assertion. Does that make it clear?
> They never restrict your freedom 4 with their EULA. Only availability of future binaries. All already received binaries have their licenses intact and unrestricted, even if you break the EULA.
And
> You can exercise freedom 4, but only if you never use any updated version of this software again
To me those seem 100% equivalent in what they do, I’m asking you to explain the difference which is obvious to you, but not to me.
I never say already received binaries have their licence violated. I actually never ever said the licence is violated at all, that was in my premise before the IANAL part.
You can exercise freedom 4, but only if you never use any version of this software released after exercising that freedom.
Red Hat is doing the same thing, threatening to cut off the relationship if you decide to exercise one of the GPL's freedoms. Counts as a restriction in my book.