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 11:29:17 -0700
From:	"David Schwartz" <davids@...master.com>
To:	<linux-kernel@...r.kernel.org>
Subject: RE: how about mutual compatibility between Linux's GPLv2 and GPLv3?

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?

The fundamental problem is this: Any proposed mutually compatible license
must either permit or prohibit Tivoization. If it prohibits it, then it's no
different from changing the kernel license to GPLv3. If it allows it, then
it's no different from the GPLv2 and it would be suicide to the whole
purpose of the GPLv3 for it to be compatible with it.

DS

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