From: Dan Williams <dcbw@redhat.com>
To: Jouni Malinen <j@w1.fi>
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: Sun, 16 Dec 2007 18:10:10 -0500 [thread overview]
Message-ID: <1197846610.7302.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20071216181159.GP5698@jm.kir.nu>
On Sun, 2007-12-16 at 10:11 -0800, Jouni Malinen wrote:
> On Sun, Dec 16, 2007 at 12:49:14PM -0500, Dan Williams wrote:
>
> > Yeah, I was going to propose that on Friday but got side-tracked. What
> > would require a new key type? Are there some firmwares that _only_
> > accept the WPA passphrase? Because if there aren't (PS3 accepts WPA hex
> > keys too) then the supplicant could just pass the hex key. Not quite
> > sure what you mean here with "new key type".
>
> It is a new key type regardless of whether it is PSK or passphrase. The
> current key types (IW_AUTH_CIPHER_*) are WEP40, TKIP, CCMP, and WEP104..
Ah, it's a different key because it's not set _during_ the 4-way
handshake, but just sent to the fw directly and the fw handles it,
right?
> I don't know whether there are any Linux drivers that would use WPA
> passphrase, but at least the Mac OS X driver interface seems to only use
> passphrase for WPA-Personal, so it is apparently possible to design such
> a architecture ;-). Anyway, I would be fine with just adding
> IW_AUTH_CIPHER_PMK for now (and the new capability to figure out whether
> this is needed). That PMK would be PSK for WPA-Personal, but it could
> also be used as PMK for WPA-Enterprise, so the more generic PMK name.
Sounds good.
Dan
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jouni Malinen <j@w1.fi>
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: Sun, 16 Dec 2007 18:10:10 -0500 [thread overview]
Message-ID: <1197846610.7302.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20071216181159.GP5698-mgr6C1c9aYeHXe+LvDLADg@public.gmane.org>
On Sun, 2007-12-16 at 10:11 -0800, Jouni Malinen wrote:
> On Sun, Dec 16, 2007 at 12:49:14PM -0500, Dan Williams wrote:
>
> > Yeah, I was going to propose that on Friday but got side-tracked. What
> > would require a new key type? Are there some firmwares that _only_
> > accept the WPA passphrase? Because if there aren't (PS3 accepts WPA hex
> > keys too) then the supplicant could just pass the hex key. Not quite
> > sure what you mean here with "new key type".
>
> It is a new key type regardless of whether it is PSK or passphrase. The
> current key types (IW_AUTH_CIPHER_*) are WEP40, TKIP, CCMP, and WEP104..
Ah, it's a different key because it's not set _during_ the 4-way
handshake, but just sent to the fw directly and the fw handles it,
right?
> I don't know whether there are any Linux drivers that would use WPA
> passphrase, but at least the Mac OS X driver interface seems to only use
> passphrase for WPA-Personal, so it is apparently possible to design such
> a architecture ;-). Anyway, I would be fine with just adding
> IW_AUTH_CIPHER_PMK for now (and the new capability to figure out whether
> this is needed). That PMK would be PSK for WPA-Personal, but it could
> also be used as PMK for WPA-Enterprise, so the more generic PMK name.
Sounds good.
Dan
next prev parent reply other threads:[~2007-12-16 23:11 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
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 [this message]
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=1197846610.7302.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=geoffrey.levand@am.sony.com \
--cc=j@w1.fi \
--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.