From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Subject: [RFC PATCH 0/2] cfg80211: minor updates for WPA3 OWE support
Date: Thu, 13 Feb 2020 09:07:04 +0000 [thread overview]
Message-ID: <20200213090657.28841-1-sergey.matyukevich.os@quantenna.com> (raw)
Hello Johannes and all,
This patch series suggests a couple of minor changes related to WPA3 OWE.
One patch adds define for OWE AKM suite. Another patch disables strict
validation for UPDATE_OWE command.
When strict validation is enabled, kernel rejects appropriate hostapd
command with 'unsupported attribute' error message. This message is
related to status attribute NL80211_ATTR_STATUS_CODE, which is added
to nl80211 messsage using nla_put_u16.
Let me know if disabling strict validation is now frowned upon and
there is a more appropriate way to make existing hostapd command to
work properly.
Regards,
Sergey
Sergey Matyukevich (2):
cfg80211: skip strict validation for UDPATE_OWE command
ieee80211: add WPA3 OWE AKM suite selector
include/linux/ieee80211.h | 1 +
net/wireless/nl80211.c | 1 +
2 files changed, 2 insertions(+)
--
2.11.0
next reply other threads:[~2020-02-13 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 9:07 Sergey Matyukevich [this message]
2020-02-13 9:07 ` [RFC PATCH 1/2] cfg80211: skip strict validation for UDPATE_OWE command Sergey Matyukevich
2020-02-13 9:12 ` Johannes Berg
2020-02-13 11:13 ` Sergey Matyukevich
2020-02-13 11:16 ` Johannes Berg
2020-02-13 11:21 ` Sergey Matyukevich
2020-02-13 11:26 ` Johannes Berg
2020-02-13 11:43 ` Sergey Matyukevich
2020-02-13 12:10 ` Johannes Berg
2020-02-13 9:07 ` [RFC PATCH 2/2] ieee80211: add WPA3 OWE AKM suite selector Sergey Matyukevich
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=20200213090657.28841-1-sergey.matyukevich.os@quantenna.com \
--to=sergey.matyukevich.os@quantenna.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