@sally >What if it executes but does nothing more than return 1 and stops because the server rejects connection? And the server is completely proprietary, mind you, you can't host your own.
That isn't really relevant to the concept of tivotization, which is hardware that refuses to execute binaries that aren't signed by the OEM.

The GPLv2 doesn't set out any requirements when it comes to accessing a remote server.

With proper free software, you don't even want to use someone else's malicious server - you want to to use your own server, or one hosted by a trustworthy party.

The GPLv3 does try to work around that problem by stating; "Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network."