From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: Avraham Stern <avraham.stern@intel.com>
Subject: Re: [RFC v2 2/2] cfg80211: support 4-way handshake offloading for 802.1X
Date: Tue, 28 Mar 2017 12:50:37 +0200 [thread overview]
Message-ID: <5274c4b4-9bce-208c-e3f2-640d54b81a30@broadcom.com> (raw)
In-Reply-To: <20170221123758.5339-2-johannes@sipsolutions.net>
On 21-2-2017 13:37, Johannes Berg wrote:
> From: Avraham Stern <avraham.stern@intel.com>
>
> Add API for setting the PMK to the driver. For FT support, allow
> setting also the PMK-R0 Name.
>
> This can be used by drivers that support 4-Way handshake offload
> while IEEE802.1X authentication is managed by upper layers.
So looking at wpa_supplicant RFC patches I see that it now diverts
driver_nl80211_set_key() for ALG_PMK case to the new api. So why not
extending CMD_NEW_KEY to support ALG_PMK?
Regards,
Arend
next prev parent reply other threads:[~2017-03-28 10:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 12:37 [RFC v2 1/2] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK Johannes Berg
2017-02-21 12:37 ` [RFC v2 2/2] cfg80211: support 4-way handshake offloading for 802.1X Johannes Berg
2017-02-24 8:08 ` Arend Van Spriel
2017-03-02 8:59 ` Johannes Berg
2017-03-02 10:50 ` Arend Van Spriel
2017-03-28 10:50 ` Arend Van Spriel [this message]
2017-03-31 11:50 ` Johannes Berg
2017-03-31 12:39 ` Arend Van Spriel
2017-03-31 12:42 ` Johannes Berg
2017-03-31 18:40 ` Arend Van Spriel
2017-02-21 14:43 ` [RFC v2 1/2] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK Jouni Malinen
2017-02-21 14:46 ` Johannes Berg
2017-02-21 14:47 ` Johannes Berg
2017-02-23 9:56 ` Arend Van Spriel
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=5274c4b4-9bce-208c-e3f2-640d54b81a30@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=avraham.stern@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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.