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.0802290929590.17889@woody.linux-foundation.org>
Date:	Fri, 29 Feb 2008 09:33:47 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Pavel Roskin <proski@....org>
cc:	Zan Lynx <zlynx@....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

On Fri, 29 Feb 2008, Pavel Roskin wrote:
> 
> Actually, it's a flawed comparison.  The only thing ndiswrapper exports
> to NDIS modules is NDIS API.  GPLONLY symbols are only used to implement
> that API in the code that's under GPL.  That's the code you can fork,
> change and redistribute.

.. and it's stuill just a wrapper.

A fairly thick one, but still...

More importantly, none of the people arguing against this at all even 
reacted to my suggestion for how to fix things *properly* in my original 
email. Which just means that you're apparently not interested in actually 
fixing this, you're just trying to disagree about some interpretation of 
GPLONLY.

In other words: the next person who can't even be bothered to tell what 
symbols are involved and why they haven't asked whether those symbols 
could instead be relaxed, automaticaly will go into my "flamers" filter, 
and just stay there. Then you can complain as much as you like, and I'll 
never see it.

		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/