On Thu, 2008-02-07 at 02:13 +0100, Johannes Berg wrote: > How would you design implementing support secure peer links? It seems > that to do that much of the mesh bookkeeping would need to be done by > wpa_supplicant instead of the kernel. In fact, maybe it should always do > it and much of this code be migrated into wpa_supplicant's userspace > MLME? We definitely would implement security in user space but have not decided yet were to draw the line. I think that it makes sense at least to have path discovery in-kernel, since there is a lot of activity on them (each path is rebuilt every few seconds and there can be many of them) and many path discovery frames just need to be forwarded and do not have to be transferred to user space. > Peer link establishment, mesh path updating etc. could all be done in > wpa_supplicant's userspace MLME, no? If we add all this to the kernel > now, would we have to reimplement it in the userspace MLME to support > secure peer links? AFAIK, it would only be necessary to move part of the peer link establishment to user space. Path discovery takes place after the peer links have been established. -- Luis Carlos Cobo Rus GnuPG ID: 44019B60 cozybit Inc. -- Luis Carlos Cobo Rus GnuPG ID: 44019B60 cozybit Inc. - 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
