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 11:15:37 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Dan Williams <dcbw@...hat.com>,
	Jean Tourrilhes <jt@...gret.hpl.hp.com>,
	"John W. Linville" <linville@...driver.com>
Cc:	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 Mon, 02 Oct 2006 12:58:24 -0400
Dan Williams <dcbw@...hat.com> wrote:

> On Mon, 2006-10-02 at 18:50 +0200, Norbert Preining wrote:
> > On Mon, 02 Okt 2006, Norbert Preining wrote:
> > > > The main features of the latest beta is WE-21 support (long/short
> > > > retry, power saving level, modulation), enhanced command line parser
> > > > in iwconfig, scanning options, more WPA support and more footprint
> > > > reduction tricks
> > > 
> > > Bingo. I build the new 29-pre10 and everything is working.
> > 
> > Sorry, that was over-optimistic. still same behaviour as with the Debian
> > v28 version.
> > 
> > The last character is cut of from wpa_supplicant. I have to set the
> > essid by hadn with
> > 	"real-essid "
> > mark the space at the end!
> 
> 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.

It doesn't sound like it'll be too hard to arrange for the kernel to
continue to work correctly with old userspace?
-
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/