From: James Prestwood <prestwoj@gmail.com>
To: John Brandt <brandtwjohn@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 00/11] Basic SAE support for AP mode
Date: Mon, 22 Apr 2024 06:52:14 -0700 [thread overview]
Message-ID: <13851d8a-e91d-47e8-b9c1-0b1e7369edba@gmail.com> (raw)
In-Reply-To: <20240421125050.6649-1-brandtwjohn@gmail.com>
Hi John,
On 4/21/24 5:50 AM, John Brandt wrote:
> This set of patches adds basic SAE support for IWD in AP mode. It has
> been tested by connecting to IWD AP using wpa_supplicant. Note that this
> does not yet correspond to WPA3, since WPA3 would also require the
> support of Management Frame Protection.
>
> Normal client functionality has also been confirmed to still work. After
> applying these patches it remains possible for IWD client to connect to
> WPA3/SAE network.
>
> Remaining TODOs are to include better sanity-checking of received
> frames.
I took a quick pass and I'm impressed you took the initiative to
implement this. I do need to take a closer look from the spec side of
things but overall it looks good.
Assuming we are compliant with the spec my only concern merging this
would be the TODOs. You do mention this is experimental and certain
checks are not done, but you'd be surprised at the number of people
using IWD in AP mode. The minute we merge this we're going to have
people using it, which in its current form would be insecure. I think we
first need to get the frame verification implemented as well as MFP. But
anyways, this is a good start and I'll give it a full review when I have
some time, hopefully this week.
Thanks,
James
>
> John Brandt (11):
> ap: ability to advertise PSK and SAE
> ap: accept PSK/SAE in auth depending on config
> sae: add function sae_set_group
> sae: refactor and add function sae_calculate_keys
> sae: make sae_process_commit callable in AP mode
> sae: verify offered group in AP mode
> sae: support reception of Confirm frame by AP
> ap: add support to handle SAE authentication
> ap: enable start of 4-way HS after SAE
> eapol: support PTK derivation with SHA256
> eapol: encrypt key data for AKM-defined ciphers
>
> src/ap.c | 135 +++++++++++++++++++++++++++++++++-------
> src/eapol.c | 58 ++++++++++++-----
> src/sae.c | 175 +++++++++++++++++++++++++++++++++-------------------
> 3 files changed, 265 insertions(+), 103 deletions(-)
>
next prev parent reply other threads:[~2024-04-22 13:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 12:50 [PATCH 00/11] Basic SAE support for AP mode John Brandt
2024-04-21 12:50 ` [PATCH 01/11] ap: ability to advertise PSK and SAE John Brandt
2024-04-21 12:50 ` [PATCH 02/11] ap: accept PSK/SAE in auth depending on config John Brandt
2024-04-24 12:05 ` James Prestwood
2024-04-21 12:50 ` [PATCH 03/11] sae: add function sae_set_group John Brandt
2024-04-24 12:05 ` James Prestwood
2024-04-21 12:50 ` [PATCH 04/11] sae: refactor and add function sae_calculate_keys John Brandt
2024-04-24 12:06 ` James Prestwood
2024-04-21 12:50 ` [PATCH 05/11] sae: make sae_process_commit callable in AP mode John Brandt
2024-04-24 12:08 ` James Prestwood
2024-04-21 12:50 ` [PATCH 06/11] sae: verify offered group " John Brandt
2024-04-21 12:50 ` [PATCH 07/11] sae: support reception of Confirm frame by AP John Brandt
2024-04-24 12:08 ` James Prestwood
2024-04-21 12:50 ` [PATCH 08/11] ap: add support to handle SAE authentication John Brandt
2024-04-24 12:06 ` James Prestwood
2024-04-21 12:50 ` [PATCH 09/11] ap: enable start of 4-way HS after SAE John Brandt
2024-04-21 12:50 ` [PATCH 10/11] eapol: support PTK derivation with SHA256 John Brandt
2024-04-21 12:50 ` [PATCH 11/11] eapol: encrypt key data for AKM-defined ciphers John Brandt
2024-04-22 13:52 ` James Prestwood [this message]
2024-04-24 12:07 ` [PATCH 00/11] Basic SAE support for AP mode James Prestwood
2024-04-29 0:04 ` John Brandt
2024-04-29 12:00 ` James Prestwood
2024-04-30 23:27 ` KeithG
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=13851d8a-e91d-47e8-b9c1-0b1e7369edba@gmail.com \
--to=prestwoj@gmail.com \
--cc=brandtwjohn@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