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]

Date:	Sun, 8 Apr 2012 15:57:09 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Luis R. Rodriguez" <mcgrof@...jolero.org>
Cc:	"Ted Ts'o" <tytso@....edu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	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>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK

> >From the work with SFLC on ath5k a while ago we learned that dual
> licensing BSD/GPL is legally equivalent to licensing under the BSD
> license, dual licensing should be used when licensing a project / file
> under incompatible licenses. Dual licensing BSD/GPL can also confuse

Dual licensing avoids some confusions, it also removes the worry about
possible unanticipated incompatibility. Right now if a court somewhere
says "Hey you know what - BSD and GPL are not compatible because XYZ" the
fact it is dual licensed avoids problems.

> Well, I am arguing that "Dual BSD/GPL" is a stupid practice that has
> plagued the community and only has brought confusion. Its not needed
> and if one wants to share with the BSD community one should simply use
> the BSD license.

Which then creates the risk question. This *has* happened before although
not with a court. Long ago the FSF used to maintain the fiction that
advertising clause BSD was GPL compatible. When the lawyers looked at it
in detail they decided this was not the case and also came up with some
fun abuses to demonstrate the point.

> license. This is just for a file though.. but are we to keep extending
> this list for every new module license that is GPL-Compatible? That
> seems rather cumbersome.

It only really matters if you are trying to be clear about dual use code
- for example some of the wireless code shared with BSD and the DRI code
where it's intentionally available in both universes. At the time some
folks wanted it to be clear their code was dual licensed and didn't want
to tag it "GPLv2". That may well in truth be more about politics than law
but it's hardly unreasonable to respect authors requests when they can
easily be handled.

> As for run time... I *personally* actually believe all Linux kernel
> modules are GPL at runtime :D I'm not the one who argues that

So just mark your modules "GPLv2"

Feel free to change all those you are the sole owner for, but for
anything else go via the legal team of the relevant company and/or get
the owner to provide the change with appropriate sign off.

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/