I can't enable EAP-FAST support in wpa_supplicant (which is needed for
NetworkManager to support EAP-FAST) unless we apply Jouni's OpenSSL patch. It's
been around for quite a while but upstream never seems to comment on it. The
upstream openssl issue is:
There's a patch in wpa_supplicant git that applies to openssl 0.9.8 too,
attached here. Thoughts?
Created attachment 291197 [details]
Patch exposing functionality that wpa_supplicant needs for EAP-FAST
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Unfortunately no news from upstream. And I don't want to commit to adding the non-upstream patch.
Closing then. We can reconsider if upstream takes the patch.
*** Bug 209339 has been marked as a duplicate of this bug. ***
Finally, this was applied to HEAD
rt for the issue http://rt.openssl.org/index.html?q=1574
2008-Nov-15 18:18 1.1457 Check-in : PR: 1574 Submitted by: Jouni Malinen <firstname.lastname@example.org> Approved by: email@example.com
Ticket override support for EAP-FAST. By steve. (diff)
Changes can be viewed here
Whee! Now we can potentially add support to NM too, though how exactly we auto-detect whether openssl was built with EAP-FAST, and thus whether wpa_supplicant supports it, is anyone's guess...
Do you need build-time or run-time autodetection?
(In reply to comment #31)
> Do you need build-time or run-time autodetection?
runtime; but wpa_supplicant has the facility to report the EAP methods it supports, so I think we're OK here. Basically, we build OpenSSL with EAP-FAST support, build wpa_supplicant with EAP-FAST support against that OpenSSL, and then NetworkManager will runtime-query the supplicant to determine if EAP-FAST is available.
Of course, this doesn't solve the issue where, in the connection editor, you can always configure an EAP-FAST connection even if the computer you're currently on doesn't support it. But that's the same as if you have an old wifi card that doesn't support WPA, you should still be able to make a WPA connection and use that with a WPA capable card later. We just need better error reporting here so that when you do try to activate an EAP-FAST connection on a machine that isnt' built with EAP-FAST support, you get (a) can't and (b) get a message to that effect.
I plan to make package with the upstream patch backported to Fedora 11. It will require a SONAME bump though.
Support is missing in F9 and F10 as well for EAP-FAST.
Yes, the patch only went upstream in the past few weeks.
Unfortunately it breaks ABI so it is not possible to push the patch to F9,10.
I've backported the patch from 0.9.9 branch to the 0.9.8j which is now in rawhide.
(In reply to comment #42)
> Fixed in 'openssl-0.9.8k-7.el6', included in compose 'RHEL6.0-20091102.0'.
> Moving to ON_QA.
If QA has a problem testing this, if this could be made available to me, I would be willing to test it with an existing client network using EAP-FAST.
Jason, we lack infrastructure currently to test this bug properly. As RHEL6 Beta is public, could you please help us test this issue?
We lack infrastructure for this, Sanity Only testing. Hopely Jason will help us to test this one.
Yes, I have RHEL6Beta downloaded and have been testing in a VM. I'll just need to do some LVM work to install it natively on my host and get my client's permission to test on their EAP-FAST network.
I have my client's permission to test this on their EAP-FAST network and access to their Cisco AP and RADIUS server (Cisco ACS) which it passes authentication to.
However, I do not see EAP-FAST as an option in Network Manager. Right-clicking on NetworkManager icon, Edit Connections - Wireless (tab) - Add - Wireless Security (tab) - Security: WPA & WPA2 Enterprise
At this point the next step is to set the Authentication type. The drop-down box supports TLS, LEAP, Tunneled TLS (TTLS), and Protected EAP (PEAP), but there is no EAT-FAST option.
$ rpm -q openssl
$ rpm -qa | grep -i network
$ rpm -qa | grep wpa
$ rpm -q kernel
$ uname -a
Linux rhel6b1 2.6.32-19.el6.i686 #1 SMP Tue Mar 9 18:10:40 EST 2010 i686 i686 i386 GNU/Linux
Are we sure that EAP-FAST is now enabled in NetworkManager?
Jason, according to bug 209339 which is still assigned NM hasn't got EAP-FAST support yet. Setting needinfo on Dan Williams.
Dan, openssl seems to be supporting EAP-FAST now but NM does not.
Dan, could you please answer comment #52?
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.