linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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]

Message-ID: <87sl8ms9z5.fsf@graviton.dyn.troilus.org>
Date:	Wed, 20 Jun 2007 15:26:54 -0400
From:	Michael Poole <mdpoole@...ilus.org>
To:	david@...g.hm
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Tomas Neme <lacrymology@...il.com>,
	"Linux-Kernel\@Vger. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

david@...g.hm writes:

> this is very much NOT true. if you take the source the provide you can
> compile a kernel that will run on the tivo, the only thing you have to
> do (on some models) is to change the bios to skip the step that checks
> if the kernel has been tampered with.

If we are opining whether Tivo provided complete source code for their
Linux kernel images, the requirement to change non-GPLed software as a
condition to exercise GPL-protected rights speaks for itself.

Out of curiosity, what do you have to do on models besides those?  Are
newer models more or less restrictive in what they run?  If newer
models are more restrictive, I think that also speaks to whether Tivo
thinks it is conveying complete source code.

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/