| 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
| ||
|
Message-ID: <1268392583.4828.8.camel@jlt3.sipsolutions.net> Date: Fri, 12 Mar 2010 03:16:23 -0800 From: Johannes Berg <johannes@...solutions.net> To: Johannes Berg <johannes@...solutions.net> Cc: Valdis.Kletnieks@...edu, linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org Subject: Re: Weird wireless/wpa_supplicant screw-up. On Fri, 2010-03-12 at 03:14 -0800, Johannes Berg wrote: > On Mon, 2010-03-08 at 17:22 -0500, Valdis.Kletnieks@...edu wrote: > > (This could be user error/userspace bug, feel free to point me in the right > > direction if you think so. Hopefully somebody knows what I've broken this > > time...) > > > > Fedora Rawhide as of this morning, 2.6.33-mmotm0304 kernel, wpa_supplicant-0.6.8-8.fc13.x86_64 > > wireless-tools-29-5.1.fc12.x86_64. Dell Latitude E6500, Intel 5100AGN card. > > > > So I finally get a few spare cycles, and re-try getting WPA2 working on our > > enterprise wireless network, and wpa_supplicant reports it completed > > successfully and set the keys, > > and does it work? The iwlist stuff could just be a reporting error... In fact, it's not even an error, it's perfectly normal because we use that key for RX only since that's the group key ... So if there is a problem, iwlist is completely unsuitable for diagnosing it. johannes -- 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/
Powered by blists - more mailing lists