linux-kernel - Re: [PATCH] module: Clarify GPL-Compatible is OK

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]

Message-ID: <20120407200355.6be37c34@pyramind.ukuu.org.uk>
Date:	Sat, 7 Apr 2012 20:03:55 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Luis R. Rodriguez" <mcgrof@...jolero.org>
Cc:	rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
	Keith Packard <keithp@...thp.com>,
	Ralf Baechle <ralf@...ux-mips.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Stephen Hemminger <shemminger@...tta.com>,
	"John W. Linville" <linville@...driver.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK

> You do not need to make dual licenses when licenses are compatible
> with each other, and in fact at times this can confuse developers / legal.

Firstly you are out of order touching the licensing tags of other vendors
code. Absolutely and utterly. So nobody should for example be touching an
Intel MODULE_LICENSE() tag without the say so of Intel legal.

Secondly there are specific reasons this was done. For one it protects us
from the FSF doing insane things - which is always useful. For the second
it avoids ambiguity about licensing and it avoid assorted problems where
'compatible' isn't really good enough.

Consider the case of

Take MIT source
Is it GPL compatible ?
	Yes
Add GPL Compatible tag
Compile
Ship user the binary (under the MIT license), lock the source away

Conside also the case of

Public domain
Put into kernel
Oh look no patent transfer clause
Sue recipient of kernel

There are good legal reasons we did it the way we did. This shouldn't be
changed without a proper legal evaluation.

Dual Foo/GPL is not the same as GPL compatible.

NAK

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