linux-kernel - Re: [PATCH] module.h: add copyleft-next >= 0.3.1 as GPL compatible

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:	Wed, 29 Jun 2016 15:01:22 -0700
From:	"Luis R. Rodriguez" <mcgrof@...nel.org>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ciaran Farrell <ciaran.farrell@...e.com>,
	Christopher De Nicolo <christopher.denicolo@...e.com>,
	Richard Fontana <fontana@...rpeleven.org>,
	Discussion and development of copyleft-next 
	<copyleft-next@...ts.fedorahosted.org>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Alan Cox <alan@...ux.intel.com>,
	"Theodore Ts'o" <tytso@....edu>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] module.h: add copyleft-next >= 0.3.1 as GPL compatible

On Wed, Jun 29, 2016 at 2:43 PM, Paul Bolle <pebolle@...cali.nl> wrote:
> On wo, 2016-06-29 at 21:05 +0200, Luis R. Rodriguez wrote:
>> I haven't seen any objections or questions, so just a friendly *poke*.
>
> At the end of the day, what matters most is whether a module is GPL v2
> compatible. So why are the specific license idents for the various GPL
> v2 compatible licenses actually needed?

Long ago I reached similar conclusion and question, and therefore
proposed a simple GPL-Compatible tag then as a replacement [0]. A few
agreed [1], but others had a lot of reasons why we need to be explicit
about tags for new licenses. I recommend the full thread reading if
you are interested about more details, to me perhaps the best
explanation of why we need explicit tags is the points Alan raised
over historic incompatibilities and also of course new
incompatibilities found [2]. Finding compatibility requires work and
due diligence. That work was done here and as such a new tag is added.

[0] https://lkml.kernel.org/r/1333757482-16204-1-git-send-email-mcgrof@frijolero.org
[1] https://lkml.kernel.org/r/20120407002723.GA14568@kroah.com
[2] https://lkml.kernel.org/r/20120408181227.5d9430d9@pyramind.ukuu.org.uk

  Luis