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:	Mon, 2 Oct 2006 21:47:02 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	jt@....hp.com
Cc:	Andrew Morton <akpm@...l.org>, Dan Williams <dcbw@...hat.com>,
	"John W. Linville" <linville@...driver.com>,
	Norbert Preining <preining@...ic.at>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	hostap@...oo.com, linux-kernel@...r.kernel.org,
	ipw3945-devel@...ts.sourceforge.net
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Monday, 2 October 2006 20:55, Jean Tourrilhes wrote:
> On Mon, Oct 02, 2006 at 11:15:37AM -0700, Andrew Morton wrote:
> > On Mon, 02 Oct 2006 12:58:24 -0400
> > > 
> > > You have a mismatch between your wireless-tools, your kernel, and/or
> > > wpa_supplicant.  WE-21 uses the _real_ ssid length rather than the
> > > kludge of hacking off the last byte used previously.  Please ensure that
> > > your tools, driver, and kernel are using WE-21.
> > > 'cat /proc/net/wireless' should tell you what your kernel is using.
> > > Getting the driver WE is a bit harder and you may have to look at the
> > > source.
> > 
> > Jean, John: the amount of trouble which this change is causing is quite
> > high considering that we're not even at -rc1 yet.  It's going to get worse.
> 
> 	We have to split between the different issues we have seen.
> 	Tools issue (the wpa_supplicant problem). -> those can only be
> fixed by people upgrading. Fortunately, there are not so many tools
> affected, and new version of those tools were released last
> April/May. As I said, most distro have those in the pipe.
> 	In-Kernel driver issues (the Orinoco driver problem). -> those
> can be patched and fixed as we go along. I would not worry about
> those.
> 	Out-of-kernel issues (the ipw3945 driver problem). -> those
> drivers need to be updated. That's the problem of living outside the
> kernel. Very often those drivers are reactive with respect to kernel
> API changes, rather than pro-active, so there is not much we can do.
> 
> > It doesn't sound like it'll be too hard to arrange for the kernel to
> > continue to work correctly with old userspace?
> 
> 	Actually, it's impossible. New userspace can work across both
> version, old userspace fails on new version.

<rant>
Well, please tell me now what number of people actually _will_ upgrade?

And if they don't, will they use the -rc kernels?  No, they won't, because
of the apparent wireless breakage.

This way we loose quite a few testers and the entire development
process is affected, and that's _only_ because you have decided it
will be _convenient_ to change the ABI.  However, such changes affect
_everyone_ and in a wrong way, except for a few people who actually want the
change.  They cause more damage than they are worth, so they should be avoided
at all reasonable cost.

It would be fair to introduce the change when distributions actually ship the
userland tools capable of handling it, but not _now_.
</rant>

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller
-
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/