linux-kernel - Re: GPLv3 Position Statement

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: <1159515173.3309.373.camel@pmac.infradead.org>
Date:	Fri, 29 Sep 2006 08:32:53 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	tridge@...ba.org
Cc:	James Bottomley <James.Bottomley@...elEye.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: GPLv3 Position Statement

On Fri, 2006-09-29 at 15:51 +1000, tridge@...ba.org wrote:
> I actually think they were already in violation with TiVo version 1,
> as they were using binary kernel modules. Although it is possible to
> have a kernel module which is not a derivative work of the kernel (as
> address space and linking concerns are only "rules of thumb", not true
> tests for a derivative work), I think that their modules were in fact
> pretty clearly derived works. I can say this partly because I have
> disassembled a few of them and looked at them in great detail. 

It's simpler than that. They were in violation even if you don't
consider their module to be a derived work, because they distributed it
as part of a larger whole which was based on Linux -- and thus the GPL
extends to "each and every part regardless of who wrote it."

Binary-only modules on their own are extremely dubious, but binary-only
modules shipped as _part_ of an embedded product, in conjunction with a
Linux kernel, are a clear violation of the licence.

"If identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it."

-- 
dwmw2

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