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: <47C87460.2030705@davidnewall.com>
Date:	Sat, 01 Mar 2008 07:38:48 +1030
From:	David Newall <davidn@...idnewall.com>
To:	Pavel Roskin <proski@....org>
CC:	"John W. Linville" <linville@...driver.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	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

Pavel Roskin wrote:
> On Sat, 2008-03-01 at 07:10 +1030, David Newall wrote:
>   
>> John W. Linville wrote:
>>     
>>> On Fri, Feb 29, 2008 at 02:39:38PM -0500, Pavel Roskin wrote:
>>>   
>>>       
>>>> I doubt ndiswrapper will ever be ported to the
>>>> userspace.  It's much more likely that some other approach will be used.
>>>>     
>>>>         
>>> Maybe it should be -- that might solve a lot of problems
>>>       
>> Maybe it's time to rename it from "ndiswrapper" to "NdisWrapper".
>>
>> How stupid do you have to be to not see that it will be fixed in any way
>> necessary.
>>     
>
> I'm quite sure that something like that is going to be the short term
> fix.  Still, it would be nice to have a more long term solution, the one
> that tries to resolve the tensions rather than hide them.  I'm not sure
> it's possible, but just trying to negotiate could help find
> understanding

I think there's a political agenda, and that's something that nobody can
solve.  The simplest solution is to change the name it uses on a regular
basis, and that something relatively  unimportant.  People will still
call it ndiswrapper, but it will identify itself to the kernel as
wrappythingy, and then ndisthingy, and then wrapndis.  Heck, make it
purely random.  Solve the problem for all time.

It's a stupid problem promulgated by stupid people, and I use the word
"stupid" in it's most pejorative sense.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ