linux-kernel - Re: wpa supplicant/ipw3945, ESSID last char missing

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]

Date:	Wed, 4 Oct 2006 17:08:18 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Jean Tourrilhes <jt@....hp.com>
Cc:	Linus Torvalds <torvalds@...l.org>, Jeff Garzik <jeff@...zik.org>,
	Lee Revell <rlrevell@...-job.com>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	Norbert Preining <preining@...ic.at>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	johannes@...solutions.net
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Wed, Oct 04, 2006 at 12:52:29PM -0700, Jean Tourrilhes wrote:
> On Wed, Oct 04, 2006 at 12:21:46PM -0700, Linus Torvalds wrote:

> > The person you merged through explicitly said that if he had realized what 
> > you did, he wouldn't have merged.
> 
> 	I did not merge through Jeff.

You did, just indirectly.  I was directly upstream from you.

For the record, I did not fully comprehend that we would be breaking
existing tools (and their users) -- I certainly should have, but I
did not.  I apologize both to you for being part of this scenario I
inadvertantly allowed to unfold and to the users who experienced the
resulting breakage.

This was the second time I took patches for extending WE, and I have
received nothing but grief from either set of patches.  Even had
things gone smoothly, WE was already hated near universally.  WE has
survived based on being "good enough" for a long time.  But I think
it is safe to say that if WE were not already in the kernel, it would
have little chance of making it in today.

All the legitimate options for extending WE now amount to forking a
new API.  But work is already underway on a WE replacement.  I think
the best option is to invest in that replacement, and a compatibility
layer to support older WE-aware applications.  Please see the nl80211
and cfg80211 currently on the netdev list.

I do not intend or expect to take any more WE enhancment patches.
Only bug fixes to WE will be accepted from now onward.

Jean, I thank you for your long-running contributions.  I hope this
will not discourage you from further participation.

Thanks,

John
-- 
John W. Linville
linville@...driver.com
-
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/