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, 3 Oct 2006 19:21:00 -0700
From:	Jouni Malinen <jkmaline@...hut.fi>
To:	Jean Tourrilhes <jt@....hp.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jeff Garzik <jeff@...zik.org>,
	"John W. Linville" <linville@...driver.com>,
	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
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Tue, Oct 03, 2006 at 12:49:57PM -0700, Jean Tourrilhes wrote:

> 	No, it's not. But as soon as *some part* of WE-21 appears in
> the kernel, the userspace expect the ESSID change. If we want to have
> WE-21 without the ESSID change, we need to fix userspace.

Or leave WIRELESS_EXT at 20 and come up with a new way of versioning any
future changes in WE.. Yes, having two different mechanisms for version
number is ugly, but it could prevent userspace breakage.

(And based on the other messages in this thread, it might be useful to
include the userspace program's idea of the version in those new
commands to allow multiple interface versions to be supported by the
kernel).

-- 
Jouni Malinen                                            PGP id EFC895FA
-
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/