linux-kernel - Re: [PATCH v2] 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87r3anzfuw.fsf@rustcorp.com.au>
Date:	Thu, 21 Jul 2016 15:34:39 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	"Luis R. Rodriguez" <mcgrof@...nel.org>,
	linux-kernel@...r.kernel.org, ciaran.farrell@...e.com,
	christopher.denicolo@...e.com, fontana@...rpeleven.org,
	copyleft-next@...ts.fedorahosted.org, gnomes@...rguk.ukuu.org.uk,
	alan@...ux.intel.com, tytso@....edu, pebolle@...cali.nl,
	hpa@...or.com, joe@...ches.com
Subject: Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible

Greg KH <gregkh@...uxfoundation.org> writes:
>> Adding a license here implies we accept that it's actually GPLv2
>> compatible.  And IANAL.
>
> Note, at least lawyer has signed off on this.
>
> I'd like to see Richard do so as well.

Sure, but as I said before I'm not applying it until we have accepted
in-tree code which needs it.

If there's consensus that the kernel needs to accept YA license, I will
abide by it as module maintainer.  But I won't endorse it myself.

Thanks,
Rusty.