lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 20 Jun 2007 12:33:34 -0700 (PDT)
From:	david@...g.hm
To:	Michael Poole <mdpoole@...ilus.org>
cc:	Tomas Neme <lacrymology@...il.com>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Wed, 20 Jun 2007, Michael Poole wrote:

> Tomas Neme writes:
>
>>> It's simple: they don't provide _complete_ source code.  They keep the
>>> source code for the part of their Linux kernel images that provides
>>> the functionality "runs on Tivo DVRs".  The GPL requires that
>>
>> http://en.wikipedia.org/wiki/Tivoization does not agree that this is
>> the problem but rather "TiVo circumvented this goal by making their
>> products run programs only if the program's digital signature matches
>> those authorised by the manufacturer of the TiVo."
>>
>> I'm downloading the sources now.. if they compile, then you're lying
>> to me, right? Moreover, if I compile them as is, and I can run them on
>> a TiVo (let's say upgrading the machine's kernel) then you're even
>> more so..
>
> Whether the sources you download from Tivo compile says very little.
> It certainly does not mean I am wrong.  I could give you binary for
> version A and sources for version B -- and the sources would compile.
>
> The kernel you build from the source code that Tivo distributes must
> be accepted by Tivo's hardware without making other modifications (to
> Tivo's hardware or bootloader).  If that is possible, I will retract
> what I said.  If it is not possible, they are omitting part of the
> program's source code:

no, saying that the result must be acceptable to other software (in this 
case the software running in the BIOS) is not part of the source code.

David Lang

>    A "computer program" is a set of statements or instructions to be
>    used directly or indirectly in a computer in order to bring about
>    a certain result.
>    -- US Code, Title 17, Section 101
>
> Michael Poole
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ