[U-Boot] U-book and GPLv3? (fwd)

[Robin Getz]

On Wed 1 Jul 2009 07:46, Richard Stallman pondered:
> 
>     I can't see how someone can deny access to the network, while still
>     allowing anyone's software to be run on the device, without some sort
>     of key system in the networking hardware - is that what you had in mind?
> 
> This is aimed at cell phone networks: it recognizes they are allowed
> to make the network refuse to talk to a phone if the users's changes
> cause the phone to screw up the network.

There is a difference between the network not talking to you, and you not able 
to be on the network.

> 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.

The way I read that is that it is the unit you are on will have it's radio 
off, and you will not be able to use it, not the network will not talk to 
you.

You could apply the same thing to VoIP phones...

When XXXX manufacture makes a VoIP phone, they test it against various 
networking tests (all internal, since they are not required to release this 
info) to make sure that it acts "properly" on the network. They sign this 
image to make sure that flash is not failing. If something doesn't match the 
signature - how can the manufacture believe that is doesn't violate the rules 
or protocols of ethernet? So - it denies access to the network - by not 
booting that image. That is the only way that they can deny access to the 
network all SoC variations that I'm familiar with.

This is in no way trying to interperate the GPL3 for others (that is for 
lawyers to do) - but just a question from an interested developer - to me - 
it seems like tivo all over again. All Tivo needs to do is just make the 
network a piece of their application - and they have an out...

-Robin