linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK
Date: Tue, 21 Feb 2017 12:34:46 +0100	[thread overview]
Message-ID: <c38019e8-32b5-5fa2-1da7-8022cbb62b13@broadcom.com> (raw)
In-Reply-To: <1487673603.2215.3.camel@sipsolutions.net>

On 21-2-2017 11:40, Johannes Berg wrote:
> On Tue, 2017-02-21 at 11:32 +0100, Arend Van Spriel wrote:
>> On 21-2-2017 11:09, Johannes Berg wrote:
>>> From: Eliad Peller <eliad@wizery.com>
>>>
>>> Let drivers advertise support for station-mode 4-way handshake
>>> offloading with a new
>>> NL80211_EXT_FEATURE_4WAY_HANDSHAKE_OFFLOAD_STA
>>> flag.
>>
>> I find use of the term OFFLOAD a bit redundant as it is implied by
>> its presence anyway.
> 
> Fair enough, we can remove that.
> 
>>> Add a new NL80211_ATTR_PMK attribute that might be passed as part
>>> of NL80211_CMD_CONNECT command, and contain the PSK (which is the
>>> PMK, hence the name.)

It is also added to NL80211_CMD_ASSOCIATE. Maybe worth mentioning.

>>> The driver/device is assumed to handle the 4-way handshake by
>>> itself in this case (including key derivations, etc.), instead
>>> of relying on the supplicant.

What I am also missing is how to deal with NL80211_CMD_CONNECTED event
signalling. Should that be given after (un)successful completion of the
4-way handshake or should we have a separate event for that?

Regards,
Arend

>>> This patch is somewhat based on this one (by Vladimir Kondratiev):
>>> https://patchwork.kernel.org/patch/1309561/.
>>
>> It also looks quite like this one we posted a while ago [1]. Our bad
>> that we did not follow-up :-p
> 
> Indeed, I was looking for the better link (had gmane recorded in the
> internal commit log) and found a few that all looked the same ... :)
> 
> Would this work for you? We should have wpa_supplicant support too, but
> need to ask Andrei to look at that.
> 
> johannes
> 

  reply	other threads:[~2017-02-21 11:34 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 [this message]
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
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=c38019e8-32b5-5fa2-1da7-8022cbb62b13@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=eliad@wizery.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 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).