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: <20070615000232.GB9463@alinoe.com>
Date:	Fri, 15 Jun 2007 02:02:32 +0200
From:	Carlo Wood <carlo@...noe.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Alexandre Oliva <aoliva@...hat.com>,
	Adrian Bunk <bunk@...sta.de>, Valdis.Kletnieks@...edu,
	Daniel Hazelton <dhazelton@...er.net>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, 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

On Fri, Jun 15, 2007 at 12:39:19AM +0100, Alan Cox wrote:
> > This is the main reason I dislike GPLwhatever: there is no notion
> > of "orginal author". You might have written 99% of the code, that
> 
> Every literary work (including thus software) has an author, and that
> author has certain rights which are implicit in them being author.

Like, they can release/sell the whole thing under some arbitrary
other license at their choice. But once you license it with the GPLv2,
then you can't stop anyone else (who got it under that license) from
using the code under that license anymore, as such it doesn't matter that
you are the original author.

> > doesn't matter. You have no rights whatsoever once you release
> > something under the GPL (no more than ANYOne else).
> 
> Wrong. The author has a collection of rights which vary by jurisdiction
> but which are primarily governed by the Berne Convention and its sequels
> notably TRIPS.
> 
> > The GPL is nice for the community, and for the users - but very,
> > very bad towards it's authors (taking all and every right you might
> > have). If John Doe wants to re-release the whole kernel under
> 
> You must be using a different GPL to the rest of us.

You actually had me check the license of the linux kernel :p
But really - it has this paragraph that I was refering to in most of it's
source files:

* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.

I might be wrong, but I always thought that that meant that John Doe
is free to redistribute the software under version 3 of the License,
as published by the FSF.

There are source files in the kernel without this phrase, ie - they
just say: * This file is released under the GPL.

But then the paragraph from COPYING kicks in, reading:

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

Any, 'any version' probably includes version 3 as well.

Finally, there are file that don't mention the GPL at all, for example
kernel/sys.c just says:

 *  Copyright (C) 1991, 1992  Linus Torvalds

But - if it weren't GPL-ed then that would be a violation of the GPL-ed
of the rest (Nevertheless, I think the license header should be added
to those files).

> > GPLv3, then all he needs is a website and some bandwidth.
> 
> And a very good lawyer (oh and a GPL3 as there isn't one yet...)

I really don't like license discussions - and after reading in the
mailinglist FAQ that license posts are taboo here - I was partly annoyed,
partly amazed to see this HUGE flood of mails with as subject line
"Dual-Licensing Linux Kernel with GPL V2 and GPL V3"

I am sorry that I drew the apparently wrong conclusion that GPL V3
is a pressing reality.

> Alan

-- 
Carlo Wood <carlo@...noe.com>
-
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/