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: <alpine.LFD.1.00.0802290807110.17889@woody.linux-foundation.org>
Date:	Fri, 29 Feb 2008 08:08:42 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Pavel Roskin <proski@....org>
cc:	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



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.

> > If it loads non-GPL modules, it shouldn't be able to use GPLONLY symbols.
> 
> This is not the original intention of GPLONLY.  GPLONLY exists to prevent
> loading of modules that are proprietary, but can be considered to be Linux
> derivatives due to their use of Linux specific API.

Exactly. And ndiswrapper loads proprietary modules.

You're not following the argument. There was a reason ndiswrapper was 
marked for tainting. 

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