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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 2 Feb 2007 15:53:06 +0100
From:	"Paul Rolland" <rol@...917.net>
To:	"'Jan Engelhardt'" <jengelh@...ux01.gwdg.de>,
	"'Linux Kernel Mailing List'" <linux-kernel@...r.kernel.org>
Cc:	"'Andrew Morton'" <akpm@...l.org>,
	"'Jon Masters'" <jonathan@...masters.org>,
	"'Alexey Dobriyan'" <adobriyan@...il.com>
Subject: RE: [PATCH] Ban module license tag string termination trick

Hello,

> will be written to the object file will be "license=GPL\0for 
> nothing\0". 
> When this is interpreted back again in the kernel module 
> loader, it is 
> read as "license=GPL", having circumvented the loading mechanism and 
> having wrongfully access to GPL symbols. According to Alexey [ 
> http://lkml.org/lkml/2006/10/27/233 ], LinuxAnt is one vendor to use 
> this trick.

If that is really one important point, why not simply adding a :
MODULE_IS_UNDER_GPL_LICENSE("yes|no")
and a
MODULE_IS_UNDER_GPL_LIKE_LICENSE("yes|no")

or use 0 and 1 instead of yes and no, and thus clearly avoid all the
C string mess ?

Regards,
Paul

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