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: Thu, 18 May 2017 12:40:12 +0200 [thread overview]
Message-ID: <1495104012.2553.3.camel@sipsolutions.net> (raw)
In-Reply-To: <4e0672aa-51bc-115f-32b7-b1a8eb747e5b@broadcom.com> (sfid-20170518_122908_051835_AC8F2BE6)
On Thu, 2017-05-18 at 12:29 +0200, Arend Van Spriel wrote:
> On 18-5-2017 11:22, Johannes Berg wrote:
> > On Thu, 2017-05-18 at 10:18 +0200, Arend Van Spriel wrote:
> > >
> > > > We should therefore probably set the expectation that wpa_s -
> > > > if
> > > > it's new enough - always uses the offloaded functionality and
> > > > always sets the WANT_1X. Then this is even better with such
> > > > drivers, since they can immediately reject the connect()
> > > > command if
> > > > want_1x isn't set.
>
> Getting back at this. With "always" you mean for every connect()
> regardless whether it is using 1X or PSK?
No, I just meant it would never use the non-offloaded functionality for
1X, as long as wpa_s was new enough to support it.
The same consideration kinda applies to (non-)offloaded 4-way-HS for
PSK though I guess, with some drivers (devices) not able to not offload
it.
> You mean adding a nl80211 command in which user-space can indicate
> what features it supports? Do you want to use the same feature bits
> on both sides to easily determine the combined feature set?
> ext_feature does not really have much overlapping so not sure if it
> adds value.
No, I meant that we have NL80211_EXT_FEATURE_4WAY_HANDSHAKE_STA_1X
today, but then we might need also
NL80211_EXT_FEATURE_HOST_4WAY_HANDSHAKE_STA_1X.
Come to think of it though, I guess the fact that the NEW_KEY command
isn't support would already indicate that.
johannes
next prev parent reply other threads:[~2017-05-18 10:40 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 [this message]
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
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=1495104012.2553.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).