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]

Date:	Thu, 21 Jun 2007 16:56:03 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	davids@...master.com
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?

On Jun 21, 2007, "David Schwartz" <davids@...master.com> wrote:

> Alexandre Oliva wrote:

>> However, if GPLv3 had a permission to combine/link with code under
>> GPLv2, *and* Linux (and any other projects interested in mutual
>> compatibility) introduced an additional permission to combine/link
>> with code under GPLv3 (or even GPLv3+, constrained by some condition
>> if you will), then:

> Wouldn't that defeat the entire purpose of the GPLv3? Couldn't I take any
> GPLv3 program, combine it with a few lines of Linux code, and Tivoize the
> result?

No.  This is not permission to relicense.  This is permission to
combine.  Each author still gets to enforce the terms of her own code.
So a tivoizer would have to take out the code licensed under the
GPLv3, and use only the code that permits tivoization.  Same as today,
but without the possibility of cooperation for licensees who don't
tivoize.

Sorry if this wasn't obvious, it was for me.

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