On 02/01/2013 07:32, Antonio Quartulli wrote: > Hi Johannes, > > On Fri, Dec 28, 2012 at 03:51:08 +0100, Johannes Berg wrote: >> Anyway this part is really confusing. If userspace is handling auth >> frames, should the kernel really mark the station as authenticated? What >> then is the point in handling auth frames in userspace?? In IBSS mode, the "auth" state is essentially a no-op with the current code, just saying. I do open system authentication in userspace, partly to fix these race conditions in a clean way, and to have more control over it in a more convenient way. That way, it is possible to hack things like retrying authentication at the user will if it failed the first time. I can also handle stations that do not answer auth frames much easier, such as skipping open system authentication if the other station engage actually tries to authenticate with us. >> Any chance we could converge on a single implementation here? >> > > Maybe yes :) > > I think that leaving the station not AUTHenticated and let userspace do so would > be the best approach..but then we need a way to enable userspace to do it :) What would happen to old userspace that expect that to be done in the kernel ? -- 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
