On Fri, Feb 25, 2011 at 05:32:37PM -0800, Thomas Pedersen wrote:
> From: Javier Cardona <javier@xxxxxxxxxxx>
> @@ -529,7 +529,9 @@ ieee80211_default_mgmt_stypes[NUM_NL80211_IFTYPES] = {
> [NL80211_IFTYPE_MESH_POINT] = {
> + .rx = BIT(IEEE80211_STYPE_ACTION >> 4) |
> + BIT(IEEE80211_STYPE_AUTH >> 4) |
> + BIT(IEEE80211_STYPE_DEAUTH >> 4),
This seems to be pointing towards processing the full Authentication
frame in user space. However, some other patches in this series seemed
to be extending the NL80211_CMD_AUTHENTICATE mechanism to allow SAE to
be implemented on top of it. Which direction is being taken here? Or are
both mechanisms going to be used depending on iftype?
For non-mesh cases, I would probably prefer NL80211_CMD_AUTHENTICATE
extension for the station vif to continue with the style we started for
FT. The AP vif is already handling the full Authentication frame in user
space, so that is fine to for SAE, too.
--
Jouni Malinen PGP id EFC895FA
--
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
