From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.01.org
Subject: [PATCH] eapol: do not parse RSN for WPA1 in 1 of 4
Date: Thu, 17 Oct 2019 16:43:16 -0700 [thread overview]
Message-ID: <20191017234316.4271-1-prestwoj@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
A recent change checked the return value of ie_parse_rsne_from_data
inside the ptk 1/4 handler. This seemed safe, but actually caused
the eapol unit test to fail.
The reason was because eapol was parsing the IEs assuming they were
an RSN, when they could be a WPA IE (WPA1 not WPA2). The WPA case
does not end up using the rsn_info at all, so having rsn_info
uninitialized did not pose a problem. After adding the return value
check it was found this fails every time for WPA1.
Since the rsn_info is not needed for WPA1 we can only do the RSN
parse for WPA2 and leave rsn_info uninitialized.
---
src/eapol.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/eapol.c b/src/eapol.c
index 6f04dbc5..349e824f 100644
--- a/src/eapol.c
+++ b/src/eapol.c
@@ -1106,8 +1106,11 @@ static void eapol_handle_ptk_1_of_4(struct eapol_sm *sm,
pmkid = handshake_util_find_pmkid_kde(EAPOL_KEY_DATA(ek, sm->mic_len),
EAPOL_KEY_DATA_LEN(ek, sm->mic_len));
- if (ie_parse_rsne_from_data(own_ie, own_ie[1] + 2, &rsn_info) < 0)
- goto error_unspecified;
+ if (!sm->handshake->wpa_ie) {
+ if (ie_parse_rsne_from_data(own_ie, own_ie[1] + 2,
+ &rsn_info) < 0)
+ goto error_unspecified;
+ }
/*
* Require the PMKID KDE whenever we've sent a list of PMKIDs in
--
2.17.1
next reply other threads:[~2019-10-17 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 23:43 James Prestwood [this message]
2019-10-17 23:48 ` [PATCH] eapol: do not parse RSN for WPA1 in 1 of 4 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=20191017234316.4271-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.