From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 02/10] network: pass scan_bss into network_load_psk
Date: Tue, 5 Dec 2023 07:46:39 -0800 [thread overview]
Message-ID: <20231205154647.1778389-2-prestwoj@gmail.com> (raw)
In-Reply-To: <20231205154647.1778389-1-prestwoj@gmail.com>
For adding SAE password identifiers the capability bits need to be
verified when loading the identifier from the profile. Pass the
BSS object in to network_load_psk rather than the 'need_passphrase'
boolean.
---
src/network.c | 60 +++++++++++++++++++++++++--------------------------
1 file changed, 30 insertions(+), 30 deletions(-)
diff --git a/src/network.c b/src/network.c
index f203834c..79f964b2 100644
--- a/src/network.c
+++ b/src/network.c
@@ -594,8 +594,34 @@ generate:
return -EIO;
}
-static int network_load_psk(struct network *network, bool need_passphrase)
+static inline bool __bss_is_sae(const struct scan_bss *bss,
+ const struct ie_rsn_info *rsn)
{
+ if (rsn->akm_suites & IE_RSN_AKM_SUITE_SAE_SHA256)
+ return true;
+
+ return false;
+}
+
+static bool bss_is_sae(const struct scan_bss *bss)
+{
+ struct ie_rsn_info rsn;
+
+ memset(&rsn, 0, sizeof(rsn));
+ scan_bss_get_rsn_info(bss, &rsn);
+
+ return __bss_is_sae(bss, &rsn);
+}
+
+static int network_load_psk(struct network *network, struct scan_bss *bss)
+{
+ /*
+ * A legacy psk file may only contain the PreSharedKey entry. For SAE
+ * networks the raw Passphrase is required. So in this case where
+ * the psk is found but no Passphrase, we ask the agent. The psk file
+ * will then be re-written to contain the raw passphrase.
+ */
+ bool is_sae = bss_is_sae(bss);
const char *ssid = network_get_ssid(network);
enum security security = network_get_security(network);
size_t psk_len;
@@ -616,7 +642,7 @@ static int network_load_psk(struct network *network, bool need_passphrase)
}
/* PSK can be generated from the passphrase but not the other way */
- if (!psk || need_passphrase) {
+ if (!psk || is_sae) {
if (!passphrase)
return -ENOKEY;
@@ -778,25 +804,6 @@ bool network_get_force_default_owe_group(struct network *network)
return network->force_default_owe_group;
}
-static inline bool __bss_is_sae(const struct scan_bss *bss,
- const struct ie_rsn_info *rsn)
-{
- if (rsn->akm_suites & IE_RSN_AKM_SUITE_SAE_SHA256)
- return true;
-
- return false;
-}
-
-static bool bss_is_sae(const struct scan_bss *bss)
-{
- struct ie_rsn_info rsn;
-
- memset(&rsn, 0, sizeof(rsn));
- scan_bss_get_rsn_info(bss, &rsn);
-
- return __bss_is_sae(bss, &rsn);
-}
-
int network_can_connect_bss(struct network *network, const struct scan_bss *bss)
{
struct station *station = network->station;
@@ -959,7 +966,7 @@ int network_autoconnect(struct network *network, struct scan_bss *bss)
switch (security) {
case SECURITY_PSK:
- ret = network_load_psk(network, bss_is_sae(bss));
+ ret = network_load_psk(network, bss);
if (ret < 0)
goto close_settings;
@@ -1285,20 +1292,13 @@ static struct l_dbus_message *network_connect_psk(struct network *network,
struct l_dbus_message *message)
{
struct station *station = network->station;
- /*
- * A legacy psk file may only contain the PreSharedKey entry. For SAE
- * networks the raw Passphrase is required. So in this case where
- * the psk is found but no Passphrase, we ask the agent. The psk file
- * will then be re-written to contain the raw passphrase.
- */
- bool need_passphrase = bss_is_sae(bss);
if (!network_settings_load(network)) {
network->settings = l_settings_new();
network->ask_passphrase = true;
} else if (!network->ask_passphrase)
network->ask_passphrase =
- network_load_psk(network, need_passphrase) < 0;
+ network_load_psk(network, bss) < 0;
l_debug("ask_passphrase: %s",
network->ask_passphrase ? "true" : "false");
--
2.34.1
next prev parent 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 [PATCH 01/10] scan: parse password identifier/exclusive bits James Prestwood
2023-12-05 15:46 ` James Prestwood [this message]
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-2-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