Skip to contentSkip to conversation

freebox possible GPL violation

DISCUSSION Pierre Michon 13 participants 28 messages Oct 5, 2005 – Oct 11, 2005

lore
Share & tools
lore
#0 lore raw

Hi,

Quoted 3 lines

I'm sorry, I must be a bit stupid but I don't see any GPL violation here... Could you be a bit more specific on what kind of code, Free is keeping under his foot ?

Sorry I realise that my first post wasn't clear.

The fimware that is used with the freebox is a Linux system. So in the firmware there is the GPL Linux kernel and all the GPL software listed on [1] (busybox for example).

Users can't download nor binary firmware nor source code of GPL software.

The binary firmware is downloaded by the freebox when a new version is available. This is done on an unknow server with an unknow protocol.

So free keep the Linux kernel modification they have made. You could see some of the log of their modification on [2] and [3]. They also don't provide the source for the GPL userspace software they include in the firmware.

Pierre

[1] http://www.f-b-x.net/#firm
[2]
http://openlogging.org:8080/sakura.(none)/max-20040524220224-60268-baea416b9b2da5c2/src?nav=index.html
[3]
http://openlogging.org:8080/chewbacca.proxad.net/rani-20040112173203-20972-c609c93690b2941a/src?nav=index.html

#1 lore raw

Hi,

Ok, I think this is cristal clear to me, now. :)

Quoted 8 lines · Pierre Michon

The fimware that is used with the freebox is a Linux system. So in the firmware there is the GPL Linux kernel and all the GPL software listed on [1] (busybox for example).

Users can't download nor binary firmware nor source code of GPL software.

Quoted 7 lines

The binary firmware is downloaded by the freebox when a new version is available. This is done on an unknow server with an unknow protocol.

So free keep the Linux kernel modification they have made. You could see some of the log of their modification on [2] and [3]. They also don't provide the source for the GPL userspace software they include in the firmware.

Your task will be to prove that the kernel they upload to your box is a modified Linux kernel (by "modified Linux kernel", I mean no modules but the kernel itself).

So, the first step would be to catch/sniff this binary image, then analyze it.

But, as long as you cannot prove that Free has done internal modifications to the Linux kernel which are not released in any way, your case is quite thin.

Regards

Signature · 4 lines
Emmanuel Fleury

Don't speculate - benchmark.
  -- Dan Bernstein
#2 lore raw
Quoted 11 lines

Your task will be to prove that the kernel they upload to your box is a modified Linux kernel (by "modified Linux kernel", I mean no modules but the kernel itself).

So, the first step would be to catch/sniff this binary image, then analyze it.

But, as long as you cannot prove that Free has done internal modifications to the Linux kernel which are not released in any way, your case is quite thin.

why?

The GPL holds modified or not...

(and that includes drivers if they are distributed together with the gpl kernel as part of a bigger work)

#3 lore raw
Quoted 7 lines · Arjan van de Ven

why?

The GPL holds modified or not...

(and that includes drivers if they are distributed together with the gpl kernel as part of a bigger work)

Because they can just add a link to www.kernel.org on the kernel 2.4.20 (as refered in http://www.f-b-x.net/#firm). I would be a quick fix for them.

Regards

Signature · 4 lines
Emmanuel Fleury

Reality continues to ruin my life.
  -- Calvin & Hobbes (Bill Waterson)
#25 lore raw
In reply to Arjan van de Ven
Quoted 12 lines · Arjan van de Ven
Quoted 11 lines

Your task will be to prove that the kernel they upload to your box is a modified Linux kernel (by "modified Linux kernel", I mean no modules but the kernel itself).

So, the first step would be to catch/sniff this binary image, then analyze it.

But, as long as you cannot prove that Free has done internal modifications to the Linux kernel which are not released in any way, your case is quite thin.

Quoted 6 lines

why?

The GPL holds modified or not...

(and that includes drivers if they are distributed together with the gpl kernel as part of a bigger work)

The unmodified kernel and the unmodified drivers are available from ftp.kernel.org and other sources, the vendor doesn't have to supply them, only tell you where you can get them if you want them.

Anything the vendor wrote in user-space is the vendor's own stuff. The vendor doesn't have to supply them at all.

Transparently upgrading across the network is a pretty good idea. It seems that the "secret" protocol they are using pissed you off so you think they must be doing something wrong.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13 on an i686 machine (5589.55 BogoMips). Warning : 98.36% of all statistics are fiction.

****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

#27 lore raw
In reply to Pierre Michon
Quoted 3 lines · Pierre Michon

[1] http://www.f-b-x.net/#firm

Quite interesting. But this is "Linus Torvalds" and not "Linus Tordval".

The only thing we can know is that they are using a 2.4.24-pre9 compiled for MIPS. But, you're right on one point, the fact that they have several version of the 2.4.24-pre9 with different sizes makes it really really suspicious.

Regards

Signature · 4 lines
Emmanuel Fleury

Please do not shoot the pianist. He is doing his best.
  -- Oscar Wilde
#26 lore raw
In reply to linux-os (Dick Johnson)
Quoted 16 lines · linux-os (Dick Johnson)
Quoted 14 lines · Arjan van de Ven
Quoted 11 lines

Your task will be to prove that the kernel they upload to your box is a modified Linux kernel (by "modified Linux kernel", I mean no modules but the kernel itself).

So, the first step would be to catch/sniff this binary image, then analyze it.

But, as long as you cannot prove that Free has done internal modifications to the Linux kernel which are not released in any way, your case is quite thin.

why?

Quoted 8 lines
Quoted 4 lines

The GPL holds modified or not...

(and that includes drivers if they are distributed together with the gpl kernel as part of a bigger work)

The unmodified kernel and the unmodified drivers are available from ftp.kernel.org and other sources, the vendor doesn't have to supply them, only tell you where you can get them if you want them.

only for non-commercial distribution!
which here isn't the case obviously

#4 lore raw
In reply to Emmanuel Fleury
Quoted 11 lines · Emmanuel Fleury
Quoted 7 lines · Arjan van de Ven

why?

The GPL holds modified or not...

(and that includes drivers if they are distributed together with the gpl kernel as part of a bigger work)

Because they can just add a link to www.kernel.org on the kernel 2.4.20 (as refered in http://www.f-b-x.net/#firm). I would be a quick fix for them.

that's not enough to satisfy the GPL conditions.

#5 lore raw
Quoted 2 lines · Arjan van de Ven

that's not enough to satisfy the GPL conditions.

It is.

Regards

Signature · 5 lines
Emmanuel Fleury

And I'm right. I'm always right, but in this case
I'm just a bit more right than I usually am.
  -- Linus Torvalds
#6 lore raw
Quoted 5 lines · Emmanuel Fleury
Quoted 2 lines · Arjan van de Ven

that's not enough to satisfy the GPL conditions.

It is.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange;
or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

they don't do a)

they don't do b)

c) is only for noncommerial distribution (not the case here) and only if they got it in a type b) before, eg it allows you to transfer a type b) in the non-commerical case.

#24 lore raw
In reply to Emmanuel Fleury
Quoted 7 lines · Emmanuel Fleury
Quoted 2 lines · Arjan van de Ven

that's not enough to satisfy the GPL conditions.

It is.

From the GPL FAQ:

==================================================
Is making and using multiple copies within one organization or company "distribution"?

No, in that case the organization is just making the copies for itself. As a consequence, a company or other organization can develop a modified version and install that version through its own facilities, without giving the staff permission to release that modified version to outsiders.
==================================================

The bottom line is the Freebox is still owned by Free when you are using it. It you "buy" it (by not giving it back and paying 400 EUR), you don't have the right anymore to plug it into free network, thus don't have access to freebox's firmware.

but please keep that away from the LKML, this is *offtopic* here. This list is about *developement* of the linux kernel..

Signature · 1 line
Vincent Hanquez
#7 lore raw
In reply to Arjan van de Ven
Quoted 24 lines · Arjan van de Ven

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange;
or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

Quoted 7 lines

they don't do a)

they don't do b)

c) is only for noncommerial distribution (not the case here) and only if they got it in a type b) before, eg it allows you to transfer a type b) in the non-commerical case.

First, it is very arguable to say that they are "distributing" the software as it does not comes with the FreeBox but is automatically downloaded at each boot through the DSLAM network (which the user is not supposed to know about).

Second, if you take the example of the LinkSys case, there was an indirect way of getting all these informations (their website) and _still_ you don't have all the informations you claimed in the boxes that LinkSys is selling but on their website.

See:
http://gnumonks.org/~laforge/weblog/2005/06/13#20050613-linksys-adsl2mue

And (LinkSys GPL Code Center):
http://www.linksys.com/servlet/Satellite?childpagename=US%2FLayout&packedargs=c%3DL_Content_C1%26cid%3D1115416836002&pagename=Linksys%2FCommon%2FVisitorWrapper

If you want to know more about the _usage_ (and in matter of justice and laws the usage is often more important than what is written down), I would suggest you take a look at the LinkSys case.

See:
- http://lkml.org/lkml/2003/6/7/164
- http://lwn.net/Articles/53780/

Regards

Signature · 4 lines
Emmanuel Fleury

My life needs a rewind/erase button.
  -- Calvin & Hobbes (Bill Waterson)
#8 lore raw
Quoted 4 lines · Emmanuel Fleury

First, it is very arguable to say that they are "distributing" the software as it does not comes with the FreeBox but is automatically downloaded at each boot through the DSLAM network (which the user is not supposed to know about).

In the US, copyright law's definitive use of "distribution" says that "to distribute copies or phonorecords of the copyrighted work to the public by sale or other stranfer of ownership, or by rental, lease, or lending" is a right reserved to the copyright owner. Saying "it's only a loan" or "it's only temporary" does not relieve any obligation under the GPL. I would imagine that law across the EU is similar.

Michael Poole

#9 lore raw
In reply to Emmanuel Fleury
Quoted 4 lines · Emmanuel Fleury

First, it is very arguable to say that they are "distributing" the software as it does not comes with the FreeBox but is automatically downloaded at each boot through the DSLAM network (which the user is not supposed to know about).

So if I tell you to download a Live CD using say bittorrent and don't tell you that this Live CD contains Linux the kernel because you're not supposed to know that, you're not entitled to get the sources?

Signature · 3 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
#10 lore raw
In reply to Emmanuel Fleury
Quoted 1 line · Emmanuel Fleury

Arjan van de Ven wrote:

[...]

Quoted 4 lines
Quoted 4 lines

they don't do a)

they don't do b)

Quoted 8 lines
Quoted 3 lines

c) is only for noncommerial distribution (not the case here) and only if they got it in a type b) before, eg it allows you to transfer a type b) in the non-commerical case.

First, it is very arguable to say that they are "distributing" the software as it does not comes with the FreeBox but is automatically downloaded at each boot through the DSLAM network (which the user is not supposed to know about).

If the box downloads a linux kernel through the DSLAM network, then someone is clearly distributing linux kernels through the DSLAM network. I would guess it is the same guys, because relying on someone else providing them with kernels is a risky business. But whoever is on the other end of the DSLAM net have to offer the source as well, because they _are_ distributing kernels.

The fact that the user isn't supposed to know how this box work doesn't change anything, of course. The GPL says those who distribute the work - it doesn't matter that they don't tell the customer that they're given a linux kernel. They still have to offer the source if asked.

Helge Hafting

#11 lore raw
Quoted 7 lines · Helge Hafting

If the box downloads a linux kernel through the DSLAM network, then someone is clearly distributing linux kernels through the DSLAM network. I would guess it is the same guys, because relying on someone else providing them with kernels is a risky business. But whoever is on the other end of the DSLAM net have to offer the source as well, because they _are_ distributing kernels.

Quoted 5 lines

The fact that the user isn't supposed to know how this box work doesn't change anything, of course. The GPL says those who distribute the work - it doesn't matter that they don't tell the customer that they're given a linux kernel. They still have to offer the source if asked.

the argument that they are making is that they are only moveing the kernel within their own companies equipment, and therefor it doesn't count as 'distribution'

agree with this argument or not, but please acknowledge this point of view rather then pretending that they have no argument at all and are just plain refusing.

David Lang

Signature · 2 lines
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
 -- C.A.R. Hoare
#12 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 19 lines
Quoted 8 lines

If the box downloads a linux kernel through the DSLAM network, then someone is clearly distributing linux kernels through the DSLAM network. I would guess it is the same guys, because relying on someone else providing
them with kernels is a risky business. But whoever is on the other end of the DSLAM net have to offer the source as well, because they _are_ distributing kernels.

Quoted 5 lines

The fact that the user isn't supposed to know how this box work doesn't change anything, of course. The GPL says those who distribute the work - it doesn't matter that they don't tell the customer that they're given a linux kernel. They still have to offer the source if asked.

the argument that they are making is that they are only moveing the kernel within their own companies equipment, and therefor it doesn't count as 'distribution'

Quoted 6 lines

agree with this argument or not, but please acknowledge this point of view rather then pretending that they have no argument at all and are just plain refusing.

David Lang

If one turns it on, doesn't turn it off, pays the 400 EUR and as a result OWNS it, then what one has is a box that at that point in time is running Linux and one is the owner of it.

// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFDRHnpBrn2kJu9P78RApviAJ9AwjF8wU+6ao/L61AC7xW/QSBRZwCaA9u1 yDDXxWQ/0MHeAS7pSg4C4rg=
=oLR8
-----END PGP SIGNATURE-----

#13 lore raw
Quoted 3 lines · Stefan Smietanowski

If one turns it on, doesn't turn it off, pays the 400 EUR and as a result OWNS it, then what one has is a box that at that point in time is running Linux and one is the owner of it.

as I said, feel free to argue against their point, but let's stop having people getting on their high horse pretending that they have no argument at all.

David Lang

Signature · 2 lines
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
 -- C.A.R. Hoare
#14 lore raw
In reply to David Lang
Quoted 9 lines · David Lang
Quoted 7 lines · Helge Hafting

If the box downloads a linux kernel through the DSLAM network, then someone is clearly distributing linux kernels through the DSLAM network. I would guess it is the same guys, because relying on someone else providing them with kernels is a risky business. But whoever is on the other end of the DSLAM net have to offer the source as well, because they _are_ distributing kernels.

Quoted 8 lines
Quoted 5 lines

The fact that the user isn't supposed to know how this box work doesn't change anything, of course. The GPL says those who distribute the work - it doesn't matter that they don't tell the customer that they're given a linux kernel. They still have to offer the source if asked.

the argument that they are making is that they are only moveing the kernel within their own companies equipment, and therefor it doesn't count as 'distribution'

Interesting argument, but it breaks for at least two reasons:
1. You can buy that box instead of just hiring it. That moves kernels "outside the company", for money even.
2. It doesn't matter if they only move kernels withing their own companys equipment. If they lend a customer equipment containing a linux kernel, then
they're lending
them a linux kernel. Lending is distribution!

Quoted 2 lines

agree with this argument or not, but please acknowledge this point of view rather then pretending that they have no argument at all and are just plain refusing.

The argument might be fine, if they were moving linux kernels into company equipment used by company personell only. (I.e. linux-powered desktops/servers/gadgets for their employees.) And it might not. Maybe they actually have to distribute source to employees too, if they request it. The GPL only mentions recipients, no exceptions for "internal company use". A company may perhaps demand that the employees never request the source, though. Or perhaps "internal use" is covered by the company being a "legal unit".

People breaking the GPL should be taken seriously. Fortunately, the solution is easy for GPL-breakers. Break someone else's license, and they have to pay damages. Break the GPL, and all you need to do is to stuff some source code onto a public (web/ftp)server - and all is fine again.

The situation is so cheap and _easy_ to rectify, that is one reason people gets so pissed off at a violation. It is not as if complying with the GPL would be any kind of burden to them.

Helge Hafting

#15 lore raw
Quoted 4 lines · Helge Hafting

Interesting argument, but it breaks for at least two reasons: 1. You can buy that box instead of just hiring it. That moves kernels "outside the company", for money even.

I might have misunderstood but I think that if you buy the hardware you cannot connect it to the DSLAM network anymore. So that only the boxes they own are connected to the DSLAM.

Quoted 4 lines

2. It doesn't matter if they only move kernels withing their own companys equipment. If they lend a customer equipment containing a linux kernel, then they're lending them a linux kernel. Lending is distribution!

Are you sure this point has been clarified in court in the past ? If not, I would bet on it (for the specific case of settop boxes).

Quoted 9 lines

The argument might be fine, if they were moving linux kernels into company equipment used by company personell only. (I.e. linux-powered desktops/servers/gadgets for their employees.) And it might not. Maybe they actually have to distribute source to employees too, if they request it. The GPL only mentions recipients, no exceptions for "internal company use". A company may perhaps demand that the employees never request the source, though. Or perhaps "internal use" is covered by the company being a "legal unit".

"internal use" is kind of a buzz word here and should probably be clarified for this kind of cases.

For now, I really don't see the flaw in Free's argument.

I mentioned in another mail the case of a mobile phone network infrastructure where the network nodes to which mobile phones are connecting are running Linux. It seems to be an "internal use" (as it never leak out of the company network) and yet providing a service to customers.

The only difference in the Freeboxes case is that the node is at the customer place (you can compare the customer's mobile phone to the customer's computer plugged on the Freebox). But the fact that you don't share your node with others and that you have it at home doesn't change the fact that the company own it.

Has been any previous similar cases in the past which went in court ?

Maybe the best attack angle would be to say that if a GPL system is interacting directly with a customer, then the source code should be distributed. But I don't see if this requirement need changes in the GPL (I'm ain't no expert).

Regards

Signature · 5 lines
Emmanuel Fleury

Always program as if the person who will be maintaining your program
is a violent psychopath that knows where you live.
  -- Unknown
#16 lore raw
Quoted 3 lines · Emmanuel Fleury

Are you sure this point has been clarified in court in the past ? If not, I would bet on it (for the specific case of settop boxes).

I _wouldn't_ bet on it....

Argh.

Regards

Signature · 5 lines
Emmanuel Fleury

Given that sooner or later we're all just going to die,
what's the point of learning about integers?
  -- Calvin & Hobbes (Bill Waterson)
#17 lore raw
In reply to Emmanuel Fleury
Quoted 13 lines · Emmanuel Fleury
Quoted 4 lines · Helge Hafting

Interesting argument, but it breaks for at least two reasons: 1. You
can buy that box instead of just hiring it. That moves kernels "outside the company", for money even.

I might have misunderstood but I think that if you buy the hardware you cannot connect it to the DSLAM network anymore. So that only the boxes they own are connected to the DSLAM.

Well, but there still is a kernel in the box that was downloaded before they bought it? Or does the box become unuseable when they buy it?

Quoted 12 lines
Quoted 7 lines

2. It doesn't matter if they only move kernels withing their own companys equipment. If they lend a customer equipment containing a linux kernel, then they're lending them a linux kernel. Lending is
distribution!

Are you sure this point has been clarified in court in the past ? If not, I would bet on it (for the specific case of settop boxes).

Licencing rules applies when copying stuff for internal use. Consider what would happen, if the company used windows
instead of linux on their boxes:
Everytime they copy windows onto a box they have to pay ms for another licence. Big companies can't jsut buy a single windows licence and copy it to all their desktops. BSA has definitely clarified that in court. Now, the ms licence specifies payments to ms. The GPL is just another licence, with slightly different terms. Instead of a payment, it specifies source availability as the "price".

There is clearly court precedent that companies have to comply with software licences when making copies for _internal_ use. GNUs licence or ms licence shouldn't matter.

Quoted 6 lines

"internal use" is kind of a buzz word here and should probably be clarified for this kind of cases.

For now, I really don't see the flaw in Free's argument.

If "when do we invoke the GPL" is hard to see, try considering "when do we have to pay" if using ordinary proprietary pay-per-instance software. You will then find that the cases are similiar.

If the company makes and distributes an internal copy of windows, then they pay ms. If the company makes and distributes an internal copy of linux, then they have to provide an internal copy of the source as well.

If I make a business out of lending windows boxes, then I have to pay licences on each box. If I lend customers linux boxes, I should lend them the source too if they requests it. Remember, even if the average customer doesn't know what software is in the box, they still have the right to make a copy of the linux kernel, because you cannot take away that right.

Quoted 7 lines

I mentioned in another mail the case of a mobile phone network infrastructure where the network nodes to which mobile phones are connecting are running Linux. It seems to be an "internal use" (as it never leak out of the company network) and yet providing a service to customers.

This is fine. Similiar to how I can run a linux-based webserver, without having to provide people with linux source. This because I don't give them the server that contains linux. But if you _sell_ one of those network nodes, then you have to provide linux source along with it.

Quoted 7 lines

The only difference in the Freeboxes case is that the node is at the customer place (you can compare the customer's mobile phone to the customer's computer plugged on the Freebox). But the fact that you don't share your node with others and that you have it at home doesn't change the fact that the company own it.

Interesting argument indeed. But consider: what would happen if the phones (or freebox) were to run windows? The distributing company would have to pay licencing fees, right?

Quoted 4 lines

Has been any previous similar cases in the past which went in court ?

There have at least been cases where companies were selling linux-powered products, and were told that they had to provide the sources. I don't know if any of them bothered going to court, simply making the source available (on a cd or webserver) is so much cheaper than that.

Quoted 6 lines

Maybe the best attack angle would be to say that if a GPL system is interacting directly with a customer, then the source code should be distributed. But I don't see if this requirement need changes in the GPL (I'm ain't no expert).

An interesting thing about the GPL is that it talks about "distributing copies", not about "selling or otherwise changing ownership".

"Distributing" a linux kernel embedded in a product owned by the company doesn't change that. Where the binary kernel go, the source should go too (if requested).

Fortunately, this licencing term is so easy to satisfy that it'd be silly to try to fight it. Stick the source on a webserver somewhere. Provide the URL in the accompagnying paper (or a README file if appropriate.) If distributing cd's, consider sticking a tarball there.

Helge Hafting

#18 lore raw
Quoted 3 lines · Helge Hafting

Well, but there still is a kernel in the box that was downloaded before they bought it? Or does the box become unuseable when they buy it?

No idea, I don't have a Freebox yet.

Quoted 9 lines

If I make a business out of lending windows boxes, then I have to pay licences
on each box. If I lend customers linux boxes, I should lend them the source too if they
requests it. Remember, even if the average customer doesn't know what software
is in the box, they still have the right to make a copy of the linux kernel, because you
cannot take away that right.

You got an extremely good point here. At least it shows why this way of doing is not "moral", but, looking at the GPL text, there is nothing stating any obligation to "pay" in any manner (money or contributions) to use and/or modify GPLed softwares.

Just to illustrate my point, in the case of an webserver, if the webmaster patch the code of his own webserver to provides his customers with a new service. Has he the obligation to redistribute this code ? Namely, his patched webserver will never get distributed. The only interaction between the customers and his webserver will be through exchanges of HTML files.

And anyway, to whom redistribute the code ? Indeed, what would do the customers with such code ? As they are only using the service without really touching the software.

Therefore, it would be nice from the webmaster to contribute with his patch, but I do think that it is his own choice to do so.

Note: Originally, the redistribution of the code was mainly to avoid customers or companies to get stuck with a "no more maintained" binaries. In the case we are looking now, as the hardware is not belonging to the customers, there is no such risk. So the protection seems to be against something else... but what ?

Quoted 5 lines

There have at least been cases where companies were selling linux-powered products, and were told that they had to provide the sources. I don't know if any of them bothered going to court, simply making the source available (on a cd or webserver) is so much cheaper than that.

LinkSys is an example. But the customers were owning the machine with everything in it (including the OS). Again, the clause on distributing the sources help to not get stuck with a piece of hardware that you own with no possibility of upgrade (remembers me the famous story of RMS and the laser printer).

Quoted 11 lines

An interesting thing about the GPL is that it talks about "distributing copies", not about "selling or otherwise changing ownership".

"Distributing" a linux kernel embedded in a product owned by the company doesn't change that. Where the binary kernel go, the source should go too (if requested).

Fortunately, this licencing term is so easy to satisfy that it'd be silly to try to fight it. Stick the source on a webserver somewhere. Provide the URL in the accompagnying paper (or a README file if appropriate.) If distributing cd's, consider sticking a tarball there.

Well, I'm really sorry to play the Devil Advocate once time more, but as far as I know all these DSL companies have big secrets because of weaknesses in their security. Being hacked at the Internet level is one thing, being hacked at the DSLAM level means a lot. Try to imagine if anybody could upload to you his own modified kernel, this means that you can tape all the internet traffic, all the phone calls, all the TV programs that you are looking at, and also probably having an easy way in to your local network (wired and wifi).

Regards

Signature · 5 lines
Emmanuel Fleury

Live as if your were to die tomorrow.
Learn as if you were to live forever.
  -- Mahatma Gandhi
#19 lore raw
Quoted 8 lines · Emmanuel Fleury

Well, I'm really sorry to play the Devil Advocate once time more, but as far as I know all these DSL companies have big secrets because of weaknesses in their security. Being hacked at the Internet level is one thing, being hacked at the DSLAM level means a lot. Try to imagine if anybody could upload to you his own modified kernel, this means that you can tape all the internet traffic, all the phone calls, all the TV programs that you are looking at, and also probably having an easy way in to your local network (wired and wifi).

Lousy security is not an excuse to violate contract or copyright law.

Michael Poole

#20 lore raw
In reply to Emmanuel Fleury
Quoted 15 lines · Emmanuel Fleury
Quoted 11 lines · Helge Hafting

If I make a business out of lending windows boxes, then I have to pay licences
on each box. If I lend customers linux boxes, I should lend them the source too if they
requests it. Remember, even if the average customer doesn't know what software
is in the box, they still have the right to make a copy of the linux kernel, because you
cannot take away that right.

Quoted 10 lines

You got an extremely good point here. At least it shows why this way of doing is not "moral", but, looking at the GPL text, there is nothing stating any obligation to "pay" in any manner (money or contributions) to use and/or modify GPLed softwares.

Just to illustrate my point, in the case of an webserver, if the webmaster patch the code of his own webserver to provides his customers with a new service. Has he the obligation to redistribute this code ?

No, because he didn't distribute any binary code.

Quoted 5 lines

Namely, his patched webserver will never get distributed. The only interaction between the customers and his webserver will be through exchanges of HTML files.

Correct, so only the licence on the html files (if any) will matter.

Quoted 4 lines

Therefore, it would be nice from the webmaster to contribute with his patch, but I do think that it is his own choice to do so.

Indeed, because he didn't distribute the webserver binary in any way. He still only got his own single (modified) copy. So he has choice. But if he starts selling "improved webserver boxes" then the GPL kicks in. Source too - the price of getting the sw for no money in the first place.

Quoted 7 lines

Note: Originally, the redistribution of the code was mainly to avoid customers or companies to get stuck with a "no more maintained" binaries. In the case we are looking now, as the hardware is not belonging to the customers, there is no such risk. So the protection seems to be against something else... but what ?

The point is forced open source. If you can do business using open-source stuff, then you shall be unable to prevent others from doing the same. This is the "price" of open source, and keeps the sw prices way down. Nobody can charge much for the open software component, because the source must be available for free so anybody capable of compiling it can create their own product.

Competition and the ability to make money then, is not about having the best sw (because it is forcibly not secret) but in providing the best service and hardware.

Quoted 8 lines
Quoted 7 lines

There have at least been cases where companies were selling linux-powered products, and were told that they had to provide the sources. I don't know if any of them bothered going to court, simply making the source available (on a cd or webserver) is so much cheaper than that.

Quoted 7 lines

LinkSys is an example. But the customers were owning the machine with everything in it (including the OS). Again, the clause on distributing the sources help to not get stuck with a piece of hardware that you own with no possibility of upgrade (remembers me the famous story of RMS and the laser printer).

Not getting stuck is one thing. Not needing to reinvent the wheel is another. Nobody need to make another linux kernel from scratch, they can instead grab the existing one and build on that. In the long run, this saves a lot of reimplementation cost for society. Instead, whe can focus on improving the software further.

Quoted 14 lines
Quoted 13 lines

An interesting thing about the GPL is that it talks about "distributing copies", not about "selling or otherwise changing ownership".

"Distributing" a linux kernel embedded in a product owned by the company doesn't change that. Where the binary kernel go, the source should go too (if requested).

Fortunately, this licencing term is so easy to satisfy that it'd be silly to try to fight it. Stick the source on a webserver somewhere. Provide the URL in the accompagnying paper (or a README file if appropriate.) If distributing cd's, consider sticking a tarball there.

Quoted 10 lines

Well, I'm really sorry to play the Devil Advocate once time more, but as far as I know all these DSL companies have big secrets because of weaknesses in their security. Being hacked at the Internet level is one thing, being hacked at the DSLAM level means a lot. Try to imagine if anybody could upload to you his own modified kernel, this means that you can tape all the internet traffic, all the phone calls, all the TV programs that you are looking at, and also probably having an easy way in to your local network (wired and wifi).

Well, then they need to secure their DSLAM setup. If it is at all vulnerable this way, then they need to fix it. Most users may be "computer dummies", but there are enough experts among them too. It only takes one leak, breakin, or reverse engineering session to break through security-by-obscurity. And when the cat is out of the bag, it is out forever.

The internet level is secure enough, when set up by competent people. Surely the same can be done at DSLAM level. This reminds me of ethernet many years ago, when people realized the possibilities of a hacked network driver. (A simple way to sniff all traffic, and inject spoofed traffic.) Easy to do these days, with a open-source kernel.
But these problems are solved - mostly with encryption to protect what must not be sniffed, and firewall routers preventing the routing of spoofed packets. With a good setup, spoofing is limited to spoof other machines on the same network, and then the local admin can set things straight.

Bad security is not an excuse for disobeying the GPL. The GPL itself states that there are no exceptions. If "other concerns" means you can't obey the GPL to the letter, then you _must_ refrain from distributing the GPLed software altogether. In such cases, the open software is not a legal option.

Very similiar to a company that cannot afford to pay licences - in that case proprietary sw is not an option. They can't just pirate anyway and get away with it because "otherwise their business model won't work and result in bankrupcy". If you can't take the "cost" of open sw, then don't use it. Fortunately, the cost is usually low. And they _can_ keep a linux device driver secret, they merely have to offer the source for the rest of the kernel.

Helge Hafting

#21 lore raw
In reply to Emmanuel Fleury

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 10 lines · Emmanuel Fleury
Quoted 3 lines · Helge Hafting

Interesting argument, but it breaks for at least two reasons: 1. You can buy that box instead of just hiring it. That moves kernels "outside the company", for money even.

I might have misunderstood but I think that if you buy the hardware you cannot connect it to the DSLAM network anymore. So that only the boxes they own are connected to the DSLAM.

Get the box, turn it on, don't turn it off, pay the 400 EUR, own the box LEAVING IT ON.

Result: You have a box that is _NOW_ running Linux and YOU own it.

If them placing the box at your place isn't considered distribution (re: your mobile phone thing) then you BUYING it would need to, due to transfer of ownership.

The fact that the box can't do what it's supposed to after you buy it is irrelevant.

// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFDRYXYBrn2kJu9P78RAkOWAJ9WpWueLnpxMJYNqzvP7iguD76VmwCgnbXC M7HrIV7fM5vsNXNzP0FY7MI=
=Yeav
-----END PGP SIGNATURE-----

#22 lore raw
In reply to Arjan van de Ven
Quoted 8 lines · Emmanuel Fleury
Quoted 5 lines
Quoted 1 line · Arjan van de Ven

that's not enough to satisfy the GPL conditions.

It is.

Quoted 7 lines

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange;

The Internet is a medium customarily used for software interchange, in
fact, it is most likely the most popular medium for that purpose. At the time the GPL was written (June 1991), it arguably was not. So you will see a lot of arguments that including a URL was not sufficient. However, now that the Internet is the most popular medium for software interchange, offering a URL is actually the *best* way to make the source code available.

Anyone who argues otherwise is just looking to make trouble for no reason
whatsoever. There is no medium you could possibly include that is more likely to be usable than a URL. The intent of this paragraph was that the software be available and easily accessible. A URL does this better than anything else.

DS

#23 lore raw
Quoted 3 lines · David Schwartz

However, now that the Internet is the most popular medium for software interchange, offering a URL is actually the *best* way to make the source code available.

As long as you can guarantee that the URL remains valid for the required 3 years, and that the exact source code used to build each released binary version is available, not just the latest source.