[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <874pl928r6.fsf@graviton.dyn.troilus.org>
Date: Thu, 14 Jun 2007 23:31:57 -0400
From: Michael Poole <mdpoole@...ilus.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Daniel Hazelton <dhazelton@...er.net>,
Alexandre Oliva <aoliva@...hat.com>,
Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
Greg KH <greg@...ah.com>,
debian developer <debiandev@...il.com>,
"david\@lang.hm" <david@...g.hm>,
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
Linus Torvalds writes:
> On Thu, 14 Jun 2007, Michael Poole wrote:
>>
>> If the DRM signature and program executable are coupled such that they
>> are not useful when separated, the implication to me is that they form
>> one work that is based on the original Program. This is beyond the
>> GPL's permission for "mere aggregation".
>
> So you want to make things like a 160-bit SHA1 hash of a binary be a
> "derived work" of that software?
No. That is why I specified "not useful when separated". I also
intentionally avoided the phrase "derived work": the legal definition
of derived work is based on entirely different factors.
If the signature is one that serves to indicate origin, to detect
tampering, or the other things you mentioned, the program's binary is
useful when separated from the signature. My objection arises when a
functionally equivalent binary -- including advertised functions such
as "runs on platform XYZ" -- cannot be produced from the distributed
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/
Powered by blists - more mailing lists