From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
linux-wireless@vger.kernel.org
Cc: Eliad Peller <eliad@wizery.com>, Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK
Date: Tue, 21 Feb 2017 13:37:31 +0100 [thread overview]
Message-ID: <1487680651.2215.5.camel@sipsolutions.net> (raw)
In-Reply-To: <c38019e8-32b5-5fa2-1da7-8022cbb62b13@broadcom.com> (sfid-20170221_123449_168516_EAA590DB)
> 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?
That's a good point. I don't think a new event really works well, but
perhaps we should extend the NL80211_TIMEOUT_* values with this? It's
not strictly a timeout, I guess, but it's not a direct rejection of the
association either.
Any thoughts?
johannes
next prev parent reply other threads:[~2017-02-21 12:37 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
2017-02-21 12:37 ` Johannes Berg [this message]
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=1487680651.2215.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=eliad@wizery.com \
--cc=j@w1.fi \
--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.