From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>, Jouni Malinen <j@w1.fi>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] cfg80211: add control port state to struct cfg80211_connect_resp_params
Date: Tue, 25 Apr 2017 20:36:58 +0200 [thread overview]
Message-ID: <1493145418.2609.5.camel@sipsolutions.net> (raw)
In-Reply-To: <b4dc7a6d-7865-1fb5-849a-0ead03a080c3@broadcom.com> (sfid-20170425_203436_553220_83783E98)
On Tue, 2017-04-25 at 20:34 +0200, Arend Van Spriel wrote:
> > > + (cr->port_state != CONTROL_PORT_STATE_UNAUTHORIZED
> > > &&
> > > + nla_put_flag(msg, NL80211_ATTR_PORT_AUTHORIZED)) ||
> > > (cr->req_ie &&
> > >
> >
> > This doesn't really make sense - why does unspecified equal
> > authorized?
>
> I was considering default behavior here for drivers that do not
> provide this information, ie. drivers not supporting 4-way handshake
> offload. So wpa_supplicant just looks for the PORT_AUTHORIZED
> attribute and deals with it without need for checking 4-way handshake
> offload is supported.
There are two such cases - the driver is old and doesn't provide it,
but of course once you see the attribute you know that's not the case.
And the case that the driver doesn't support 4-way-HS.
Can you really distinguish these though if you *don't* see the
attribute?
But anyway, if it's like mac80211 not providing the data at all, then
it would say authorized, which seems wrong since that's clearly not the
case for mac80211?
Or maybe I'm just confused.
johannes
next prev parent reply other threads:[~2017-04-25 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 21:01 [RFC] cfg80211: add control port state to struct cfg80211_connect_resp_params Arend van Spriel
2017-04-25 14:40 ` Johannes Berg
2017-04-25 18:34 ` Arend Van Spriel
2017-04-25 18:36 ` Johannes Berg [this message]
2017-04-25 18:56 ` Arend Van Spriel
2017-04-26 7:20 ` Johannes Berg
2017-04-26 18:46 ` Arend Van Spriel
2017-04-28 12:02 ` Johannes Berg
2017-04-28 12:46 ` Arend Van Spriel
2017-04-28 12:53 ` Johannes Berg
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=1493145418.2609.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.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 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).