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: <87zm31zw5v.fsf@graviton.dyn.troilus.org>
Date:	Fri, 15 Jun 2007 00:19:56 -0400
From:	Michael Poole <mdpoole@...ilus.org>
To:	david@...g.hm
Cc:	Alexandre Oliva <aoliva@...hat.com>,
	Florin Malita <fmalita@...il.com>,
	Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...sta.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

david@...g.hm writes:

> On Fri, 15 Jun 2007, Alexandre Oliva wrote:
>
>> Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
>>
>> On Jun 14, 2007, Bill Nottingham <notting@...hat.com> wrote:
>>
>>> OK. Let's take this to the simple and logical conclusion. A signed
>>> filesystem image containing both GPL and non-GPL code. From your
>>> point A, this is a derived work.
>>
>> I claim the signature is derived from the GPLed bits, yes.  Whether
>> that's a derived work, in the legal sense, I'm not qualified to say.
>
> it's also derived from the non-GPLed bits as well.
>
> so if it were a derived work in a legal sense (nessasary for your
> argument to have any legal meaning) then it's now illegal to make and
> distribute a checksum of a CD that contains software with incompatible
> licenses.

It is not necessary for the end item to be a derived work in order for
the GPL to apply.  A literal copy is not a derived work; a translation
is not a derived work; an executable version of a program is not a
derived work of its source code; and so forth.

What is necessary is that the "work based on the [GPLed] Program" be
more than a mere aggregation of the GPLed component(s) with non-GPLed
components.  The fact that part of the work-as-a-whole is a descriptor
of the GPLed part does not mean all descriptions the GPLed part are
governed by the GPL.  The critical factor is that the GPLed part will
not function properly without the DRM signature.

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/