| 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
| ||
|
Message-ID: <MDEHLPKNGKAHNMBLJOLKCENGOLAB.davids@webmaster.com> Date: Thu, 28 Sep 2006 19:29:55 -0700 From: "David Schwartz" <davids@...master.com> To: "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org> Subject: RE: GPLv3 Position Statement > In my very uninformed opinion, your problem is a very minor one. Your > "v2 or later" code won't get the license v2 removed, it will become > dual "v2 or v3" licensed. And assuming that v3 only adds restrictions > and doesn't allow the licensee any additional rights, you, as the > author, shouldn't have to worry much. > > The problem arises later. As with BSD/GPL dual licensed code, where > anyone can take the code and relicense it as either BSD or GPL, "v2 or > v3" code can get relicensed as v3 only. At this point, nothing is > lost, as the identical "v2 or v3" code still exists. But with further > development on the "v3 only" branch, you have a fork. And one that > doesn't just require technical means to get merged back, but has legal > restrictions. Unless I'm missing something, you *cannot* change the license from "v2 or later at your option" to "v3 or later". Both GPLv2 and GPLv3 explicitly prohibit modifying license notices. (Did the FSF goof big time? It's not too late to change the draft.) 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/
Powered by blists - more mailing lists