From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"hostap@lists.infradead.org" <hostap@lists.infradead.org>
Subject: Re: [PATCH V2 0/9] nl80211: add support for PTK/GTK handshake offload
Date: Mon, 29 May 2017 11:31:43 +0200 [thread overview]
Message-ID: <1496050303.2467.3.camel@sipsolutions.net> (raw)
In-Reply-To: <29d43b7d-6cb6-0734-6a52-31fa98e9c1bc@broadcom.com> (sfid-20170529_111825_524433_97F9D9F2)
Hi Arend,
> > Note that this (checking NEW_KEY) only works when you don't have
> > any split between AP/client cases. Not sure what's the case for
> > you.
>
> Late response so hopefully you recall, but what do you mean by "any
> split between AP/client cases"?
I meant the capability split - let's say you support 4-way-HS only for
client, but not for AP. Then you have to support the NEW_KEY command
for the AP case, even if you might not support non-offloaded 4-way-HS
for the client case.
So if something supports the following:
* client: offloaded 4-way-HS only
* AP: not offloaded 4-way-HS only
Then you have to support NEW_KEY (AP case) and then using NEW_KEY to
detect whether or not a wpa_s configuration option to not use offloaded
4-way-HS can be used will not work correctly.
I don't really see that this is a sensible configuration, but I could
imagine it existing if somebody "bolted on" AP functionality for a
client-side chipset or something like that.
Again, I think I'm happy to leave this up to you - this kind of
configuration option should really only be used for debugging anyway,
so just getting errors later is probably fine.
johannes
next prev parent reply other threads:[~2017-05-29 9:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:42 [PATCH V2 0/9] nl80211: add support for PTK/GTK handshake offload Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 1/9] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 2/9] cfg80211: support 4-way handshake offloading for 802.1X Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 3/9] nl80211: add authorized flag to CONNECT event Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 4/9] nl80211: add authorized flag to ROAM event Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 5/9] nl80211: remove desciption about request from NL80211_CMD_ROAM Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 6/9] brcmfmac: support 4-way handshake offloading for WPA/WPA2-PSK Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 7/9] brcmfmac: support 4-way handshake offloading for 802.1X Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 8/9] brcmfmac: switch to using cfg80211_connect_done() Arend van Spriel
2017-05-03 10:42 ` [PATCH V2 9/9] brcmfmac: provide port authorized state in CONNECT event Arend van Spriel
2017-05-17 14:19 ` [PATCH V2 0/9] nl80211: add support for PTK/GTK handshake offload Johannes Berg
2017-05-18 8:18 ` Arend Van Spriel
2017-05-18 9:22 ` Johannes Berg
2017-05-18 10:29 ` Arend Van Spriel
2017-05-18 10:40 ` Johannes Berg
2017-05-18 12:48 ` Arend Van Spriel
2017-05-19 10:21 ` Johannes Berg
2017-05-22 10:14 ` Arend van Spriel
2017-05-22 10:28 ` Johannes Berg
2017-05-29 9:18 ` Arend van Spriel
2017-05-29 9:31 ` Johannes Berg [this message]
2017-06-02 11:19 ` Arend van Spriel
2017-06-02 13:56 ` Johannes Berg
2017-06-03 8:08 ` Arend van Spriel
2017-06-09 9:08 ` Johannes Berg
2017-06-09 10:34 ` Arend van Spriel
2017-06-09 10:59 ` Johannes Berg
2017-06-09 11:21 ` 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=1496050303.2467.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=hostap@lists.infradead.org \
--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.