linux-kernel - Re: ndiswrapper and GPL-only symbols redux

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: <47A1E734.507@nortel.com>
Date:	Thu, 31 Jan 2008 09:20:20 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	David Newall <davidn@...idnewall.com>
CC:	Adrian Bunk <bunk@...nel.org>,
	Giridhar Pemmasani <pgiri@...oo.com>,
	Pavel Roskin <proski@....org>, linux-kernel@...r.kernel.org,
	Jon Masters <jonathan@...masters.org>,
	Rusty Russell <rusty@...tcorp.com.au>, rms@....org
Subject: Re: ndiswrapper and GPL-only symbols redux

David Newall wrote:
> This idea that some symbols may only be
> dynamically bound to GPL code is fallacy.

As I understand it, the point of EXPORT_SYMBOL_GPL is not so much the 
technical restriction (as you say, the module can lie or the user can 
patch the kernel) but to indicate that the kernel developers consider 
such interfaces to be internal to the kernel such that anything using it 
would be highly likely to be a "derived work" of the kernel.

It's a hint to other developers rather than a prevention measure.

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