linux-kernel - Re: [PATCH] Ban module license tag string termination trick

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:	Fri, 2 Feb 2007 10:51:23 +1000
From:	"Trent Waddington" <trent.waddington@...il.com>
To:	"Tomas Carnecky" <tom@...ervice.com>
Cc:	"Jon Masters" <jonathan@...masters.org>,
	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...l.org>,
	"Alexey Dobriyan" <adobriyan@...il.com>
Subject: Re: [PATCH] Ban module license tag string termination trick

On 2/2/07, Tomas Carnecky <tom@...ervice.com> wrote:
> Can't you put this somewhere into the documentation: it's our kernel,
> play by our rules, and our rules are, the license is what is visible in
> 'printf(license)'?

Here I was thinking the rules were: all modules must be GPL and the
jerks who make proprietary modules are just blatantly breaking the
law.  But you're right, the MODULE_LICENSE tag really does imply that
licenses other than the GPL are ok.

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