On Mon, 2013-01-07 at 14:16 +0100, Nicolas Cavallari wrote: > > if the userspace did not register for auth frames, then authentication will be > > handled in the kernel (as I'm doing/changing now), while if the userspace > > registered for such frames, then the kernel will assume that the authentication > > will be handled by the userspace somehow and will not deal with it (but again, > > in this way we need a command to let userspace set the AUTHenticated flag on a > > station). > > That means two implementations, not one. > > And even with this current patch, old wpasupplicant starts 4 way handshake as soon as the > NEW_STA event is received, even if the station is not authenticated by the kernel. I > expect that some EAPOL frames will be dropped as a result. That's all very confusing to me. Today, we have basically two ways of operating, userspace-authorization or open network. Neither of them requires AUTH frames, except SAE which uses them in userspace. In either case, there are a few ways a station can be added: 1) when mac80211 receives a data frame from a station matching the BSSID 2) when mac80211 receives a proper open network authentication frame from the station (except this is bypassed in SAE, since then userspace gets all authentication frames instead of mac80211) 3) when mac80211 receives a beacon or probe response from a station In all of these cases, the station is marked as authenticated (and associated for internal purposes, as this doesn't really exist in IBSS.) Authorization can be deferred to userspace, or done inline, depending on the "control port" setting. I think part of the reason this particular patch is so confusing is that it changes the semantics of when we add another station, based on our own authenticating with it? That's pretty confusing. The point, I thought, was to detect when a peer "silently rebooted" and thus lost all state. But in that case wouldn't we receive an unencrypted RSN handshake frame from the station, and be able to recover based on that? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
