From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 3/4] station: set handshake offload if supported
Date: Wed, 03 Mar 2021 14:50:07 -0600 [thread overview]
Message-ID: <c256b015-080c-a8ad-be18-625aa29a3ca0@gmail.com> (raw)
In-Reply-To: <20210303174730.6738-3-prestwoj@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
Hi James,
On 3/3/21 11:47 AM, James Prestwood wrote:
> When setting up the handshake check if wiphy supports handshake
> offload for PSK networks (not including SAE, for now).
> ---
> src/station.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/station.c b/src/station.c
> index 6496be10..93701e7f 100644
> --- a/src/station.c
> +++ b/src/station.c
> @@ -986,6 +986,8 @@ static struct handshake_state *station_handshake_setup(struct station *station,
> goto no_psk;
>
> handshake_state_set_pmk(hs, psk, 32);
> +
> + hs->offload_psk = wiphy_can_offload(wiphy, bss);
I actually wonder whether we need to put some of the logic from
wiphy_can_offload into wiphy_select_akm instead? Maybe the offload bit can be
an extra out parameter?
I suspect we need to implement the logic for offloaded SAE to really know what
will look best.
> }
> } else if (security == SECURITY_8021X)
> handshake_state_set_8021x_config(hs,
>
Regards,
-Denis
next prev parent reply other threads:[~2021-03-03 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 17:47 [PATCH 1/4] wiphy: add wiphy_can_offload API James Prestwood
2021-03-03 17:47 ` [PATCH 2/4] handshake: add offload member James Prestwood
2021-03-03 20:42 ` Denis Kenzior
2021-03-03 17:47 ` [PATCH 3/4] station: set handshake offload if supported James Prestwood
2021-03-03 20:50 ` Denis Kenzior [this message]
2021-03-03 17:47 ` [PATCH 4/4] netdev: offload handshake when requested James Prestwood
2021-03-03 20:41 ` [PATCH 1/4] wiphy: add wiphy_can_offload API 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=c256b015-080c-a8ad-be18-625aa29a3ca0@gmail.com \
--to=denkenz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox