From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 01/10] scan: parse password identifier/exclusive bits
Date: Tue, 5 Dec 2023 07:46:38 -0800 [thread overview]
Message-ID: <20231205154647.1778389-1-prestwoj@gmail.com> (raw)
These bits are used to communicate to the station that SAE password
identifiers are used or required.
---
src/scan.c | 20 +++++++++++++++++---
src/scan.h | 2 ++
2 files changed, 19 insertions(+), 3 deletions(-)
diff --git a/src/scan.c b/src/scan.c
index 5aa92a90..f48ffdef 100644
--- a/src/scan.c
+++ b/src/scan.c
@@ -1404,10 +1404,24 @@ static bool scan_parse_bss_information_elements(struct scan_bss *bss,
* Currently only Proxy ARP bit (12) is checked, and if
* not found, this is not a fatal error.
*/
- if (iter.len < 2)
- break;
+ if (iter.len >= 2)
+ bss->proxy_arp = test_bit(iter.data, 12);
+
+ /*
+ * 802.11-2020 Table 9-153
+ *
+ * The spec merely mentions the "exclusive" bit and
+ * doesn't enforce a requirement to check it anywhere.
+ * But if set it would indicate the AP will only accept
+ * auths when a password ID is used so store this in
+ * order to fail early if no ID is set.
+ */
+ if (iter.len >= 11) {
+ bss->sae_pw_id_used = test_bit(iter.data, 81);
+ bss->sae_pw_id_exclusive =
+ test_bit(iter.data, 82);
+ }
- bss->proxy_arp = test_bit(iter.data, 12);
}
}
diff --git a/src/scan.h b/src/scan.h
index 0db7752d..65caf41c 100644
--- a/src/scan.h
+++ b/src/scan.h
@@ -88,6 +88,8 @@ struct scan_bss {
uint8_t cost_level : 3;
uint8_t cost_flags : 4;
bool dpp_configurator : 1;
+ bool sae_pw_id_used : 1;
+ bool sae_pw_id_exclusive : 1;
};
struct scan_parameters {
--
2.34.1
next reply other threads:[~2023-12-05 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 15:46 James Prestwood [this message]
2023-12-05 15:46 ` [PATCH 02/10] network: pass scan_bss into network_load_psk James Prestwood
2023-12-05 15:46 ` [PATCH 03/10] handshake: add password identifier/setter James Prestwood
2023-12-05 15:46 ` [PATCH 04/10] network: add support for SAE password identifiers James Prestwood
2023-12-06 17:08 ` Denis Kenzior
2023-12-06 18:44 ` James Prestwood
2023-12-06 19:44 ` Denis Kenzior
2023-12-06 19:53 ` James Prestwood
2023-12-05 15:46 ` [PATCH 05/10] sae: include password identifier IE in commit James Prestwood
2023-12-05 15:46 ` [PATCH 06/10] doc: document [Security].PasswordIdentifier James Prestwood
2023-12-05 15:46 ` [PATCH 07/10] auto-t: add H2E password identifier test James Prestwood
2023-12-05 15:46 ` [PATCH 08/10] mpdu: add unknown password identifier status James Prestwood
2023-12-05 15:46 ` [PATCH 09/10] sae: add debugging for incorrect password identifier James Prestwood
2023-12-05 15:46 ` [PATCH 10/10] auto-t: throw exception if executable is missing James Prestwood
2023-12-06 17:00 ` [PATCH 01/10] scan: parse password identifier/exclusive bits Denis Kenzior
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=20231205154647.1778389-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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