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 15:43:01 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	Bernd Paysan <bernd.paysan@....de>
Cc:	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 02:03:55PM +0200, Bernd Paysan wrote:
> > I've contributed some code for the kernel (unlike yourself, AFAICT), and
> > believe me, I did so under GPL v2. The COPYING file is pretty much self
> > explanatory, so I didn't need to add any explicit license statement to
> > my code.
> 
> It's not, it's a personal comment from a misunderstanding of the GPL text. 
> It's as valid as the "closed source kernel modules are legal" comment that 
> was there some years ago.

You forgot something.  Namely, that file *without* any mentioning of
GPL or other license is either illegal to distribute at all, under
any license, *OR* inherits the default license of the project.  Which
is to say, what is stated in COPYING.

Take your pick.  For what it's worth, it would be interesting to hear
the opinion of RMS - both on how much of the kernel is possible to
distribute under v3 according to him and on the morality of your position.
-
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/