Description of problem: Error in /var/log/wpa_supplicant.log Version-Release number of selected component (if applicable): 0.3.fc17 How reproducible: Every time Steps to Reproduce: 1. Try to join WPA PEAP MSCHAPV2 Wifi Actual results: wlan0: WPA: Failed to get master session key from EAPOL state machines - key handshake aborted Expected results: Connected Additional info: I downgraded to the 0.2.fc17 and things work again.
*** Bug 811447 has been marked as a duplicate of this bug. ***
*** Bug 806128 has been marked as a duplicate of this bug. ***
*** Bug 809741 has been marked as a duplicate of this bug. ***
Adding as F17Blocker as not being able to connect to a common type of Wireless AP used by universities and businesses is a bit of a problem
Discussed at 2012-04-20 blocker review meeting - http://meetbot.fedoraproject.org/fedora-bugzappers/2012-04-20/fedora-bugzappers.2012-04-20-17.01.log.txt . Agreed that this affects enough wireless configurations to constitute a violation of Alpha criterion "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops", and so is accepted as a release blocker.
For reference, the complete affected EVR is wpa_supplicant-1.0-0.3.fc17. This only affects Fedora 17 and Rawhide, Fedora 15 and 16 not affected.
Yes, reverting to wpa_supplicant-1.0-0.2.fc17 works fixes the problem. I have been checking the repos/SRPM, wpa_supplicant-1.0-0.3.fc17 uses a snapshot from wpa-supplicant git repo. I've been following wpa-supplicant's ML and noone else complained about MSCHAP/EAPOL state machine; I'm guessing it's gone by unnoticed on the git tree. The only Fedora specific changes were a migration from libnl2 to libnl3 and dropping 0001-Fall-back-to-other-drivers-if-global-init-for-one-dr.patch .
It seems the problem was fixed by upstream. (I've modified Fedora's SRPM to compile upstream's 1.0-rc3 instead of 1.0-rc2.git20120302 and it seems to work) I can't however find the commit that fixed it -- the closest one is for TTLS/MSCHAP . So if anyone else can confirm I'd appreciate.
Is the 1.0-rc3 in yum repository now?
Nop. Just upstream.
So we, ordinary users, cannot test it.
It is now on Fedora repos, courtesy of dcbw ( http://koji.fedoraproject.org/koji/buildinfo?buildID=316646 ) P.S.: I'm an ordinary user too, I just manually updated my the RPM :p
Fixed in wpa_supplicant-1.0-0.4.fc17.x86_64 from yum
http://meetbot.fedoraproject.org/fedora-bugzappers/2012-05-04/f17-final-blocker-review-4.2012-05-04-17.00.html says: «there are reports that this has been fixed - not clear whether the update is in stable yet or not» Does this help? $ sudo yum list installed |grep wpa_supplicant wpa_supplicant.i686 1:1.0-0.4.fc17 @fedora
The latest wpa_supplicant in stable is this one: https://admin.fedoraproject.org/updates/FEDORA-2012-7053/wpa_supplicant-1.0-0.4.fc17 the update information does not mention this bug, but the package changelog does say: * Tue May 01 2012 Dan Williams <dcbw> - 1:1.0-0.4 - Update to wpa_supplicant 1.0-rc3 and Pedro and lionghostshop both suggest that is the build that fixes this bug. Given this info, I think we should close the bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers