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]

Message-ID: <20061003184016.GB17635@bougret.hpl.hp.com>
Date:	Tue, 3 Oct 2006 11:40:16 -0700
From:	Jean Tourrilhes <jt@....hp.com>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	"John W. Linville" <linville@...driver.com>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	jeff@...zik.org
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Tue, Oct 03, 2006 at 07:31:08PM +0100, Hugh Dickins wrote:
> On Tue, 3 Oct 2006, John W. Linville wrote:
> > 
> > Today's news seems to indicate that at least the major distros are
> > already shipping the updated tools, or on the verge of shipping them.
> > The window of breakage for most users looks like it will be fairly
> > small, no matter what action taken.
> > 
> > The more we can clean-up the WE API, the easier it will be to implement
> > the cfg80211 WE compatibility layer intended for wireless-dev.
> > I think WE-21 makes things better in that respect.
> 
> Please correct me if I'm wrong: isn't it the case that a few of the
> distros are now coming out with wireless_tools.28 supporting WE-20,
> but current 2.6.18-git wireless drivers are WE-21, supported only
> by wireless_tools.29.pre10?
> 
> Hugh

	wireless_tools.28 do support WE-21. I'm not a fool.

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