linux-kernel - Re: 2.6.18-git9 wireless fixes break ipw2200 association to AP with WPA

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: <20060929222410.GI22014@redhat.com>
Date:	Fri, 29 Sep 2006 18:24:10 -0400
From:	Dave Jones <davej@...hat.com>
To:	Alessandro Suardi <alessandro.suardi@...il.com>
Cc:	jt@....hp.com, "John W. Linville" <linville@...driver.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.18-git9 wireless fixes break ipw2200 association to AP with WPA

On Sat, Sep 30, 2006 at 12:04:31AM +0200, Alessandro Suardi wrote:

 > Even if so, wireless-tools would be the only package I have to
 >  build out of the FC5 distribution to keep up with the latest -git
 >  snapshot of the Torvalds kernel... I'm not especially troubled
 >  with this anyway. Perhaps you could push the Fedora folks to
 >  be a bit more up-to-date with wireless-tools in their current
 >  main version ?

We do. Frequently, because it tends to break in some manner every
single time we push a rebased kernel update.
wireless-tools v28 is in the updates repo right now, which afaik, is
already the newest available.

It's seriously unfunny to have to update fundamental userspace packages
like this when moving to a newer kernel. Especially when say for eg,
the newer kernel then has a broken sound driver, so the user goes
back to their old 'working' kernel. Oops, now they have a choice
of a kernel with broken sound, or a kernel with broken wireless.

	Dave

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