From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: Eliad Peller <eliad@wizery.com>,
Andrei Otcheretianski <andrei.otcheretianski@intel.com>,
Avraham Stern <avraham.stern@intel.com>, Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK
Date: Sat, 18 Mar 2017 08:08:09 +0100 [thread overview]
Message-ID: <ca6266ba-d399-5ea3-2faf-a4271025179f@broadcom.com> (raw)
In-Reply-To: <1489499543.10872.5.camel@sipsolutions.net>
+ Jouni
On 14-3-2017 14:52, Johannes Berg wrote:
>
>> So the 4-way hs offload patches in wpa_s RFC do not make distinction
>> between 1X and WPA-PSK. Can we expect drivers to support one, but not
>> the other? In other words do we need the flexibility in nl80211?
>
> You tell me :)
>
> We're implementing both. Andrei also raised this question on the wpa_s
> patches at my request, and nobody commented.
I see. For our firmware we can also implement both.
> I can live with combining them, but nobody better complain about it
> when they just implement one of them on their device ... :)
Indeed. These are two different use-cases so I can see merit in making
the distinction. However, for those implementing just one it would be
nice to have the distinction between 1X and WPA-PSK offload support in
wpa_supplicant as well.
Regards,
Arend
next prev parent reply other threads:[~2017-03-18 7:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 10:09 [PATCH] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK Johannes Berg
2017-02-21 10:32 ` Arend Van Spriel
2017-02-21 10:40 ` Johannes Berg
2017-02-21 11:34 ` Arend Van Spriel
2017-02-21 11:45 ` Arend Van Spriel
2017-02-21 11:46 ` Johannes Berg
2017-02-21 11:54 ` Arend Van Spriel
2017-02-28 11:06 ` Arend Van Spriel
2017-03-03 12:21 ` Johannes Berg
2017-03-03 12:47 ` Arend Van Spriel
2017-03-09 13:38 ` Arend Van Spriel
2017-03-14 13:52 ` Johannes Berg
2017-03-18 7:08 ` Arend Van Spriel [this message]
2017-02-21 12:37 ` Johannes Berg
2017-02-21 19:57 ` Arend Van Spriel
2017-02-22 12:24 ` Jithu Jance
2017-02-23 10:36 ` Arend Van Spriel
2017-02-23 10:37 ` Johannes Berg
2017-02-23 10:40 ` Arend Van Spriel
2017-02-23 10:56 ` Jithu Jance
2017-03-03 12:20 ` Johannes Berg
2017-03-03 12:44 ` Arend Van Spriel
2017-03-09 14:53 ` Jithu Jance
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=ca6266ba-d399-5ea3-2faf-a4271025179f@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=andrei.otcheretianski@intel.com \
--cc=avraham.stern@intel.com \
--cc=eliad@wizery.com \
--cc=j@w1.fi \
--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 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).