All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Dan Williams <dcbw@redhat.com>
Cc: Masakazu Mokuno <mokuno@sm.sony.co.jp>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	geoffrey.levand@am.sony.com,
	Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Subject: Re: [PATCH] PS3: gelic: Add wireless support for PS3
Date: Fri, 14 Dec 2007 17:42:44 -0800	[thread overview]
Message-ID: <20071215014244.GI5698@jm.kir.nu> (raw)
In-Reply-To: <1197637127.16724.1.camel@localhost.localdomain>

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

WARNING: multiple messages have this Message-ID (diff)
From: Jouni Malinen <j@w1.fi>
To: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Masakazu Mokuno <mokuno-DfbDroY8Xu1L9jVzuh4AOg@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	geoffrey.levand-mEdOJwZ7QcZBDgjK7y7TUQ@public.gmane.org,
	Geert Uytterhoeven
	<Geert.Uytterhoeven-osDt5Q4Chk1BDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] PS3: gelic: Add wireless support for PS3
Date: Fri, 14 Dec 2007 17:42:44 -0800	[thread overview]
Message-ID: <20071215014244.GI5698@jm.kir.nu> (raw)
In-Reply-To: <1197637127.16724.1.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

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

  reply	other threads:[~2007-12-15  1:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 12:27 [PATCH] PS3: gelic: Add wireless support for PS3 Masakazu Mokuno
2007-12-13 15:33 ` Dan Williams
2007-12-13 15:33   ` Dan Williams
2007-12-14  5:07   ` Masakazu Mokuno
2007-12-14  5:07     ` Masakazu Mokuno
2007-12-13 21:13 ` Dan Williams
2007-12-13 21:13   ` Dan Williams
2007-12-14  5:03   ` Masakazu Mokuno
2007-12-14  5:03     ` Masakazu Mokuno
2007-12-14 12:58     ` Dan Williams
2007-12-14 12:58       ` Dan Williams
2007-12-15  1:42       ` Jouni Malinen [this message]
2007-12-15  1:42         ` Jouni Malinen
2007-12-16 17:49         ` Dan Williams
2007-12-16 18:11           ` Jouni Malinen
2007-12-16 23:10             ` Dan Williams
2007-12-16 23:10               ` Dan Williams
2007-12-16 23:42               ` Jouni Malinen
2007-12-16 23:42                 ` Jouni Malinen
2007-12-21  6:17         ` Masakazu Mokuno
2007-12-21  6:17           ` Masakazu Mokuno
2007-12-14  6:48 ` David Woodhouse
2007-12-14  6:48   ` David Woodhouse
2007-12-21  9:26   ` Masakazu Mokuno
2007-12-21  9:26     ` Masakazu Mokuno
2008-01-24  5:51 ` [PATCH v2] " Masakazu Mokuno
2008-01-24  5:51   ` Masakazu Mokuno
2008-01-25  1:49   ` Dan Williams
2008-01-25  2:47     ` John W. Linville
2008-01-25  2:47       ` John W. Linville
2008-01-25  3:36       ` Masakazu Mokuno
2008-01-25  3:36         ` Masakazu Mokuno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071215014244.GI5698@jm.kir.nu \
    --to=j@w1.fi \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=dcbw@redhat.com \
    --cc=geoffrey.levand@am.sony.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mokuno@sm.sony.co.jp \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.