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: <200706152325.14244.dtor@insightbb.com>
Date:	Fri, 15 Jun 2007 23:25:13 -0400
From:	Dmitry Torokhov <dtor@...ightbb.com>
To:	Alexandre Oliva <aoliva@...hat.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 Friday 15 June 2007 17:08, Alexandre Oliva wrote:
> On Jun 15, 2007, "Dmitry Torokhov" <dmitry.torokhov@...il.com> wrote:
> 
> > On 6/15/07, Alexandre Oliva <aoliva@...hat.com> wrote:
> >> 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.
> 
> > My response to this is that by including an entire copy of specific
> > version of GPL in the release the version number was specified.
> 
> It's not that simple.  Including a copy of the license is a license
> requirement for any redistributor, yes.
> 
> But if you, a sole copyright holder, were to distribute your program,
> without any copy of the GPL, claiming "it's under the GPL", you're not
> a violator.
>

Distributing a copy of GPL is not a requirement for me as a licensor
however I did chose to include a copy of a specific version of a
specific license and did not make any other statements that is the
license for the work.
 
> Then, any redistributor adds a copy of any version of the GPL (because
> you didn't specify a version number).  At this point, is the program
> licensed by *you* only under this specific license?
>

If they did not make any changes then they have to include the earliest
version of GPL that applies. If they did modifications and chose GPLv4
they will have to include GPL v4 (if such requirement is in GPLv4) because
what good any other license will do me?
 
> Now, if you picked one of the various versions of the license, to make
> things easier for redistributors, does it mean you're choosing that
> particular version of the license,

Yes, this is my opinion.

> even though the license itself 
> says otherwise?
>

License does not say otherwise. License says that if there is an
_additional_ stipulation my the licensor then some other license
(non existing yet license) may be used. They had to use this wording
because these licensed do not exist yet. If GPL would say:

"If the Program specifies a version number of this License which
applies to it and "or BSD license", you have the option of following
the terms and conditions either of that version or of BSD license"

would you still say that BSD is allowed by default by GPL? "GPL v2
and later versions" is not different from "GPL v2 or BSD" or
"GPLv2 or CDDL".  

> > You can't say that inclusion of copy of GPL is enough to specify
> > class of licenses (all GPL) but not specific version.
> 
> I can't say either of these, indeed.  Or rather, I can, but I wouldn't
> know whether I was right ;-)
> 

-- 
Dmitry
-
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