On Mon, 2011-04-04 at 19:06 -0700, Javier Cardona wrote: > This is useful for implementing frame protection in userspace. The kernel may > request a userspace daemon to verify a frame (sent to userspace via > cfg80211_rx_mgmt()). The userspace daemon can then pass back the > verified/unprotected frame to the stack for further processing (via a > self-addressed frame sent with cfg80211_mlme_mgmt_tx()) > > We are using this for our implementation authenticated peering. 11s defines > two versions of mesh peering, the non-secure mesh peering management (MPM) and > the Authenticated Mesh Peering Exchange (AMPE). The latter is based on the > exact same state machine as MPM. It is really convenient to use the in-kernel > MPM with a minimal userspace daemon to add the security bits introduced by > AMPE. This way both secured and open mesh networks can use exact same peering > code. > > What do you think... will this fly? Seems very strange to me. I guess if you're after unification in my mind it makes more sense to declare the in-kernel state machine legacy, copy it into the userspace tool and use it even for unprotected MPM? 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
