netdev - Re: Please make CONFIG_CFG80211 harder to enable

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200612101427.20817.mb@bu3sch.de>
Date:	Sun, 10 Dec 2006 14:27:20 +0100
From:	Michael Buesch <mb@...sch.de>
To:	Pavel Roskin <proski@....org>,
	Paul Collins <paul@...ny.ondioline.org>
Cc:	"John W. Linville" <linville@...driver.com>, netdev@...r.kernel.org
Subject: Re: Please make CONFIG_CFG80211 harder to enable

On Sunday 10 December 2006 07:48, Paul Collins wrote:
> "John W. Linville" <linville@...driver.com> writes:
> 
> > On Sat, Dec 09, 2006 at 03:48:43AM -0500, Pavel Roskin wrote:
> >> Hello!
> >> 
> >> Somebody please mark CONFIG_CFG80211 in wireless-dev.git as
> >> experimental/broken/incomplete/whatever.  Not only doesn't it work, but
> >> it also breaks Wireless Extensions if enabled, even if CONFIG_D80211 is
> >> disabled.
> >> 
> >> Driver developers should know that if they enable CONFIG_CFG80211 they
> >> won't be able to debug their drivers effectifely; they'll have to fix
> >> cfg80211 first.
> >
> > Perhaps you could be more specific?  I'm sending this to you from a
> > box booted on the current (~1 week old) wireless-dev kernel using a
> > WEXT-configured ipw2200 device.
> >
> > What problems are you experiencing?  CFG80211 shouldn't interfere w/
> > WEXT if a driver doesn't support it.
> 
> I think I hit this too when I started playing with wireless-dev a week
> or so ago.  I had CFG80211 enabled and iwconfig reported "wireless

Ehm, guys?
cfg80211 is not usable in its current form because there isn't
even a damn userspace tool to interact with nl80211.
So why don't you just disable the option for the time being? That's
not too hard, I guess, and it magically fixes _all_ of your problems.

Another optional possibility would be to _implement_ the cfg80211
in d80211 and the standalone drivers, so at least the compatibility
layer works.
Come on guys, get your hands dirty instead of talking bullshit about
development code.

-- 
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html