From: Emmanuel Fleury <fleury@cs.aau.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: freebox possible GPL violation
Date: Wed, 05 Oct 2005 13:22:33 +0200 [thread overview]
Message-ID: <4343B779.8030200@cs.aau.dk> (raw)
In-Reply-To: <20051005111329.GA31087@linux.ensimag.fr>
Hi,
Ok, I think this is cristal clear to me, now. :)
Pierre Michon wrote:
>
> 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.
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
--
Emmanuel Fleury
Don't speculate - benchmark.
-- Dan Bernstein
next prev parent reply other threads:[~2005-10-05 11:24 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 11:13 freebox possible GPL violation Pierre Michon
2005-10-05 11:22 ` Emmanuel Fleury [this message]
2005-10-05 11:27 ` Arjan van de Ven
2005-10-05 11:37 ` Emmanuel Fleury
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 12:02 ` Emmanuel Fleury
2005-10-05 12:07 ` Arjan van de Ven
2005-10-05 12:29 ` Emmanuel Fleury
2005-10-05 12:45 ` Michael Poole
2005-10-05 17:11 ` Alexandre Oliva
2005-10-06 0:07 ` Helge Hafting
2005-10-06 0:49 ` David Lang
2005-10-06 1:12 ` Stefan Smietanowski
2005-10-06 2:25 ` David Lang
2005-10-06 9:20 ` Helge Hafting
2005-10-06 9:51 ` Emmanuel Fleury
2005-10-06 9:53 ` Emmanuel Fleury
2005-10-06 11:39 ` Helge Hafting
2005-10-06 13:05 ` Emmanuel Fleury
2005-10-06 13:42 ` Michael Poole
2005-10-06 14:19 ` Helge Hafting
2005-10-06 20:15 ` Stefan Smietanowski
2005-10-11 2:27 ` David Schwartz
2005-10-11 10:48 ` Graham Murray
2005-10-05 12:15 ` Vincent Hanquez
2005-10-05 11:45 ` linux-os (Dick Johnson)
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 11:50 ` Emmanuel Fleury
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 23:26 Pierre Michon
2005-10-06 12:01 Pierre Michon
2005-10-06 13:06 ` Emmanuel Fleury
2005-10-06 13:40 ` Michael Poole
2005-10-06 14:48 ` Matan Peled
2005-10-05 17:57 Pierre Michon
2005-10-05 16:06 Pierre Michon
2005-10-05 16:47 ` Emmanuel Fleury
2005-10-05 15:18 Pierre Michon
2005-10-05 15:49 ` Vincent Hanquez
2005-10-05 15:12 Pierre Michon
2005-10-05 15:08 Pierre Michon
2005-10-05 10:08 Pierre Michon
2005-10-05 10:18 ` Emmanuel Fleury
2005-10-05 8:47 Pierre Michon
2005-10-05 9:42 ` Helge Hafting
2005-10-15 9:40 ` Loic Dachary
2005-10-19 17:58 ` Pierre Michon
2005-10-20 15:29 ` Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4343B779.8030200@cs.aau.dk \
--to=fleury@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox