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: <or4pl92hv5.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Fri, 15 Jun 2007 15:27:26 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
Cc:	"Bernd Paysan" <bernd.paysan@....de>,
	"Paulo Marques" <pmarques@...popie.com>,
	"Al Viro" <viro@....linux.org.uk>,
	"Krzysztof Halasa" <khc@...waw.pl>, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 15, 2007, "Dmitry Torokhov" <dmitry.torokhov@...il.com> wrote:

> On 6/15/07, Bernd Paysan <bernd.paysan@....de> wrote:
>> On Friday 15 June 2007 13:49, Paulo Marques wrote:
>> 
>> > No, it is not "any version". It is the license specified in COPYING and
>> > nothing else.
>> 
>> COPYING says in section 9 that there may be other versions, and if you as
>> author don't specify the version, it's "any version".

> Please read this sentence over and over until it sinks:

I believe he was talking about the sentence just after the one you
quoted:

  If the Program does not specify a version number of this License,
  you may choose any version ever published by the Free Software
  Foundation.

Linux files don't all specify version 2, but Linus, Al Viro and other
authors very clearly mean their contributions to be version 2 only,
while others very clearly mean their contributions to be v2+.

The moment anyone makes copyrightable changes to any such files, and
offers them under GPLv2 only (if that's at all possible; I used to
believe so, but I've read interesting, even if surprising, arguments
indicating it might not be), the result of the modification is GPLv2
only.

So there's no doubt that the whole of the kernel is meant to be under
GPLv2 only, even if some individual authors may choose to make their
contributions available under other licenses, and be willing to make
such offers when they are legally entitled to do so.


I don't quite understand what this fuss is all about.  Even if a
majority of the Linux authors had chosen GPLv2+, or GPLvany, if any
single author makes a contribution under GPLv2 only, and that
contribution is integrated, that's a veto for distributing the whole
under any other license.  This single contributor could dictate his
choice upon others, as long as his contribution was present.

IANAL, but I believe that's how it works.  And this means Linux is
under GPLv2, no matter how much of the code in it is available under
any other versions of the GPL, or even different (but compatible)
licenses.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ