netdev - Re: [PATCH] PS3: gelic: Add wireless support for PS3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071221150228.BA41.40F06B3A@sm.sony.co.jp>
Date:	Fri, 21 Dec 2007 15:17:28 +0900
From:	Masakazu Mokuno <mokuno@...sony.co.jp>
To:	Jouni Malinen <j@...fi>
Cc:	Dan Williams <dcbw@...hat.com>, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org, geoffrey.levand@...sony.com,
	Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>
Subject: Re: [PATCH] PS3: gelic: Add wireless support for PS3

	Hi Jouni,

On Fri, 14 Dec 2007 17:42:44 -0800
Jouni Malinen <j@...fi> wrote:

> 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.

Yes, as the current WEXT did not have this feature, I could not but
design the new PS3 driver in that way.

> 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..

I had asked the hypervisor guy. Unfortunately all EAPOL frames would be
dropped by the wireless chip firmware.

-- 
Masakazu MOKUNO

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html