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: <4522A9BE.9000805@garzik.org>
Date:	Tue, 03 Oct 2006 14:19:42 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	"John W. Linville" <linville@...driver.com>
CC:	Linus Torvalds <torvalds@...l.org>,
	Lee Revell <rlrevell@...-job.com>,
	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, johannes@...solutions.net,
	jt@....hp.com
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

John W. Linville wrote:
> 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.
> 
> Finally, I already scaled-back Jean's original WE-21 patch.  I only
> anticipate minor bug fixes for WE from now on, with nl80211/cfg80211
> as the heir-apparent.
> 
> With all that said, I'd prefer to keep the existing WE-21 patches and
> add Jean's fixes ASAP.  Is this acceptable?  If not, I'll submit the
> reversions to Jeff ASAP.

I for one don't want to change the userspace ABI for this...  If I had 
realized the userspace ABI was changing (<- my fault), I wouldn't have 
merged the changes in the first place.

	Jeff


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