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:	Tue, 03 Oct 2006 11:54:36 -0400
From:	Lee Revell <rlrevell@...-job.com>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Alessandro Suardi <alessandro.suardi@...il.com>,
	Norbert Preining <preining@...ic.at>, hostap@...oo.com,
	ipw3945-devel@...ts.sourceforge.net, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Tue, 2006-10-03 at 08:38 -0400, John W. Linville wrote:
> On Mon, Oct 02, 2006 at 12:44:42PM -0400, Lee Revell wrote:
> > On Mon, 2006-10-02 at 09:21 +0000, Alessandro Suardi wrote:
> > >   we've been just through an email thread where it has been
> > >   determined that wpa_supplicant 0.4.9 (I would assume that
> > >   0.5.5 is also okay) and wireless-tools from Jean's latest
> > >   tarball are necessary to work with the recent wireless
> > >   extensions v21 that have been merged in.
> > > 
> > > What wireless-tools are you using ? 
> > 
> > This must be considered a kernel bug - it's not allowed to break
> > userspace compatibility in a stable series.
> 
> But there is no development series.  The closest thing we have is the
> merge window after each release -- which is exactly when this issue
> revealed itself.
> 
> Wireless in general (and the wireless extensions api in particular)
> is a bit of a 'whipping boy' in the Linux world.  OK, we suck.
> Everyone wants to display their wisdom by telling us how much we suck!
> We know all about it...
> 
> We have sucked, and we continue to suck -- and we are working on it.
> But, we are not going to be able to whip-up this omelette without
> breaking a few eggs.  If we can't do that during the merge windows,
> WHEN CAN WE DO IT?

This is a question for Linus, it's his rule...

Lee

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