From: Johannes Berg <johannes@sipsolutions.net>
To: Srinivas Dasari <dasaris@qti.qualcomm.com>,
Marcel Holtmann <marcel@holtmann.org>,
Jouni Malinen <jouni@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Sunil Dutt Undekari <usdutt@qti.qualcomm.com>
Subject: Re: [PATCH 1/2] cfg80211/nl80211: Optional authentication offload to userspace
Date: Tue, 19 Dec 2017 10:45:31 +0100 [thread overview]
Message-ID: <1513676731.26145.8.camel@sipsolutions.net> (raw)
In-Reply-To: <829f69319fad450db616f02de781d1a8@aphydexm01b.ap.qualcomm.com>
On Fri, 2017-12-15 at 08:51 +0000, Srinivas Dasari wrote:
> > don’t we actually need a flag in NL80211_CMD_CONNECT that indicates that userspace is able to actually handle NL80211_CMD_EXTERNAL_AUTH. It is nice >that there is feature for userspace to see if the driver supports it, but how is the driver able to offload successfully if it doesn’t know that userspace can do it.
>
> Our idea was the driver to timeout the connect for the scenarios where the external auth (SAE) status is not indicated.
> I agree with you on user space indicating this capability to the driver.
> Is it a fair idea to extend enum cfg80211_assoc_req_flags for this ?
Seems reasonable to me - though you still need to deal with userspace
not responding I guess.
johannes
prev parent reply other threads:[~2017-12-19 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 17:50 [PATCH 1/2] cfg80211/nl80211: Optional authentication offload to userspace Jouni Malinen
2017-12-13 17:50 ` [PATCH 2/2] nl80211: Allow SAE Authentication for NL80211_CMD_CONNECT Jouni Malinen
2017-12-14 19:58 ` [PATCH 1/2] cfg80211/nl80211: Optional authentication offload to userspace Marcel Holtmann
2017-12-15 8:51 ` Srinivas Dasari
2017-12-15 9:28 ` Arend van Spriel
2017-12-19 9:45 ` Johannes Berg [this message]
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=1513676731.26145.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dasaris@qti.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=usdutt@qti.qualcomm.com \
/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).