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]

Date:	Fri, 15 Jun 2007 19:52:08 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Bernd Paysan <bernd.paysan@....de>,
	Paulo Marques <pmarques@...popie.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Krzysztof Halasa <khc@...waw.pl>, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Fri, Jun 15, 2007 at 03:18:24PM -0300, Alexandre Oliva wrote:
> On Jun 15, 2007, Al Viro <viro@....linux.org.uk> wrote:
> 
> > *OR* inherits the default license of the project.
> 
> You got any case law for this?  Seriously, I could use this for
> FSFLA's IRPF2007-Livre project.
> http://fsfla.org/svnwiki/blogs/lxo/pub/freeing-the-lion

Umm...  What other license choices are there?  Seriously, if file
*does* get a license from somewhere (and if it doesn't, it can't
be distributed at all), where else would that license come from?

I can see one arguing that it shouldn't be distributed at all (and
we obviously don't want that), I can see one arguing that copyright
statement floating in root of tree in file called "COPYING" and
not tied to specific parts of that tree should apply, but I don't
see how one would argue that some other license he happens to like
should apply here.

No specific case law, but I'd expect serious [eventual] trouble for
somebody trying to slap some different license in such case.  Not
sure if anybody actually ever tried that...

IIRC, the usual argument for slapping copyright into every file is
along the lines of "making sure that it doesn't get lost when
file is lifted into another project", not "it's free for grabbing
by anyone" or "it can't be distributed at all"...
-
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/