linux-kernel - Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?

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: <20070626162541.GA5464@delft.aura.cs.cmu.edu>
Date:	Tue, 26 Jun 2007 12:25:41 -0400
From:	Jan Harkes <jaharkes@...cmu.edu>
To:	linux-kernel@...r.kernel.org
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?

On Tue, Jun 26, 2007 at 04:47:34AM -0300, Alexandre Oliva wrote:
> On Jun 26, 2007, Alexandre Oliva <oliva@....ic.unicamp.br> wrote:
> > On Jun 26, 2007, Jan Harkes <jaharkes@...cmu.edu> wrote:
> >> You could argue that they do not restrict copying, distribution
> >> and modification of the sources in general, only of the specific copy
> >> they distribute.
> 
> > "We don't oppose that you do any of these things, once you get the
> > source code.  We just make it difficult (hopefully impossible) that
> > you'll get to the source code in the first place."
> 
> Actually, they could even claim you don't need the source code to make
> modifications.  The license even says the source code is the most
> convenient form to make modifications, not the only form.  Now, that
> the others suck rocks is not their fault, is it? ;-)

GPLv2 section 3.
    The source code for a work means the preferred form of the work for
    making modifications to it.

I believe this states that the source code has to be in the preferred
form for making modifications and not some other form that sucks rocks.

As far as your argument that making it difficult or impossible to obtain
the source code could be in compliance. I don't see how (intentionally)
making something difficult could not be interpreted as a restriction so
it still violates section 6 of the GPLv2.

And yes, I do realize that you intentionally tried to come up with your
example to somehow bring tivoization to the source code. However
although the GPLv2 doesn't address the freedom to use (and specifically
does not grants the user a right to run a modified version of the
program on some specific piece of hardware), it does (try) to address
the recipients rights to copy, distribute and modify.

Jan

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