On Fri, Dec 14, 2007 at 07:58:47AM -0500, Dan Williams wrote: > On Fri, 2007-12-14 at 14:03 +0900, Masakazu Mokuno wrote: > > The PS3 wireless device does the association and 4way handshake in its > > firmware/hypervisor. No interventions between them are allowed to the guest > > OSes.
> That sort of sucks; but I guess there's not too much you can do about > it. That probably means that using wpa_supplicant + WPA is completely > out of the picture, which unfortunately makes the PS3 wireless unlike > any other card, which would require special-casing the PS3 in userspace > tools. The current wpa_supplicant development branch (0.6.x) supports drivers that want to do 4-way handshake in the driver/firmware (e.g., OSX, iPhone, this PS3 driver). In case of WPA-PSK, this doesn't really mean more than just passing through the passphrase/PSK to the association routine, but still, this allows the driver to be configured through wpa_supplicant, if desired. However, there is a part that you are not going to like.. This is likely using a private ioctl for some parts of the association requests, i.e., no -Dwext.. I would assume that this could be cleaned up, though, if WEXT would be extended a bit to allow one more enc_capa to notify whether the driver wants to take care of 4-way handshake and to allow the PSK to be configured with a new key type. PS. It would be interesting to see whether the driver/firmware/hypervisor could be convinced to allow EAPOL frames to go through between association and 4-way handshake (which would be completed by driver/firmware). This is the way I can support WPA/WPA2-Enterprise with OSX.. -- Jouni Malinen PGP id EFC895FA -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
