linux-kernel - Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols

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: <47C838C5.8030707@nortel.com>
Date:	Fri, 29 Feb 2008 10:54:29 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Pavel Roskin <proski@....org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jon Masters <jcm@...masters.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols

Linus Torvalds wrote:
> 
> On Fri, 29 Feb 2008, Pavel Roskin wrote:
> 
>>>I'm not seeing why ndiswrapper should be treated separately.
>>
>>It is already treated separately, and has been for a long time.
> 
> 
> No, I mean "separately from the thing it loads".
> 
> It loads non-GPL code, it is non-GPL.

But the GPL only applies to derivative works.  Given that ndiswrapper 
loads binaries designed for another OS, doesn't that mean that it is 
unlikely that the binaries would be impacted by the GPL?

So the portion that is a derivative work (ndiswrapper itself) is GPL, 
and it loads something that is clearly not a derivative work.  From a 
licensing standpoint how is this different than an open-source driver 
loading a proprietary firmware?

Once ndiswrapper loads the binary blob the kernel should be considered 
tainted from a debuggability standpoint, but I have some sympathy for an 
argument suggesting that ndiswrapper should be able to use GPLONLY symbols.

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/