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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0610031454420.3952@g5.osdl.org>
Date:	Tue, 3 Oct 2006 14:59:16 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	"John W. Linville" <linville@...driver.com>
cc:	Jeff Garzik <jeff@...zik.org>, jt@....hp.com,
	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, 3 Oct 2006, John W. Linville wrote:
>
> I.E.  With "WE-21 aware" tools already in the wild, it isn't now clear
> to me how WE can evolve any further than WE-20.

Well, if you get a WE-22 out soon enough, the situation will be one where 
people who are fast at updating will have a fixed version quickly, and the 
ones that aren't quick at updating will never have even seen the broken 
case.

And without any actual release kernel actually having had the issue, we 
should be pretty well off - the only people who actually saw semantics 
change were people who build their own kernels etc, and those people 
aren't the problem cases.

The users that you need to care about are the ones that upgrade rather 
seldom and/or need to maintain a stable setup for other reasons (eg it's 
not at all unheard of to have a common base release, but then have certain 
machines on the network with more modern kernels because they have new 
hardware that requires a modern kernel for support, for example: that's 
the situation where you may want to have a much older common user space, 
even if you have a new kernel).

Kernel developers tend to be happy to upgrade their user programs, and 
don't generally see it as a big problem. The people for whom it is a 
problem are elsewhere :)

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