On Wed, 2009-01-07 at 16:09 +0200, Jouni Malinen wrote: > On Wed, Jan 07, 2009 at 01:47:08PM +0100, Johannes Berg wrote: > > > Ok, I guess in that case it doesn't really matter much, though it'd be > > good to not randomly associate to an AP that has MFP enabled when we > > don't know the hardware can handle it. > > Yes and that why I was considering of a flag to notify hostapd and > wpa_supplicant about the capability.. But that would mean modifying WEXT > even more ;-). Or just adding it to nl80211, are we ever expecting to have pure wext drivers with MFP capabilities?? > > You seem to be concerned only about AP mode, while I'm not much > > concerned about that, there it's always tested explicitly by the person > > setting up the AP, but someone who's just using STA mode would now > > suddenly potentially run into problems when using an AP that is > > MFP-enabled, no? > > It is similar for both ends.. For example, wpa_supplicant does not > enable MFP on the client side by default, i.e., both hostapd and > wpa_supplicant behave the same in the sense that MFP needs to be > explicitly enabled. > > > Hence, I think adding an explicit flag (whether it needs to be exported > > to userspace I don't know) would probably be good so if the driver/hw > > really cannot handle MFP at all then we don't associate using it, no? > > MFP is negotiated in RSN IE and in case of mac80211, it would need to be > going to userspace since wpa_supplicant builds the RSN IE (and well, > hostapd obviously does the same for Authenticator side). We could a new > WEXT capability (e.g., IW_ENC_CAPA_MFP) for this, if desired.. It would > also be possible already with the current patchset to probe for this by > setting IW_AUTH_MFP and see whether the driver returns EOPNOTSUPP, so in > that sense, wpa_supplicant (and hostapd) could already figure this out > before trying to associate. Generally, the thing is that we don't really want to require people to manually enable MFP, but rather have NM set it to "enable whenever possible". That seems not workable unless we know which driver/hw supports it. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
