On Thu, 21 Jun 2007, Alexandre Oliva wrote:
On Jun 21, 2007, [EMAIL PROTECTED] wrote:
how exactly can they prevent a system that's been tampered with from
accessing their network?
By denying access to their servers? By not granting whatever is
needed to initiate network sessions?
And note, "it's been tampered with" is not necessarily enough of a
reason to cut someone off, it has to meet these requirements:
how can the server tell if it's been tampered with?
when the modification itself materially and adversely affects the
operation of the network or violates the rules and protocols for
communication across the network.
(something even you say they have a right to do)
as long as this right is not used by the software distributor to
impose restrictions on the user's ability to adapt the software to
their own needs. The GPLv3 paragraph above makes a fair concession in
this regard, don't you agree?
no, one of the rules for the network is that the software must be
certified, you are requireing the device to permit the software to be
changed to an uncertified version.(to store credit card numbers and send
them to a third party for example)
David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/