public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 2/4] network: don't allow connection to OWE AKM if disabled
Date: Thu, 24 Oct 2024 09:02:55 -0500	[thread overview]
Message-ID: <f10961fd-0839-4f65-a772-c7c850f00844@gmail.com> (raw)
In-Reply-To: <20241023182912.128388-2-prestwoj@gmail.com>

Hi James,

On 10/23/24 1:29 PM, James Prestwood wrote:
> ---
>   src/network.c | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/src/network.c b/src/network.c
> index 20d9a3dd..5a856fb4 100644
> --- a/src/network.c
> +++ b/src/network.c
> @@ -911,6 +911,9 @@ int network_can_connect_bss(struct network *network, const struct scan_bss *bss)
>   		return ret;
>   	}
>   
> +	if (IE_AKM_IS_OWE(rsn.akm_suites) && wiphy_owe_disabled(wiphy))
> +		return -EPERM;
> +

Hmm, why do we need this if we already check wiphy_owe_disabled in 
wiphy_select_akm in patch 1?

...

Ah, I guess this function doesn't perform the special case check like 
station_build_handshake_rsn() does.  That's probably why we have the problem 
with reconnects

>   	if (!config || !config->have_transition_disable) {
>   		if (band == BAND_FREQ_6_GHZ)
>   			goto mfp_no_tkip;

Regards,
-Denis

  reply	other threads:[~2024-10-24 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 18:29 [PATCH v2 1/4] wiphy: add OweDisable driver quirk James Prestwood
2024-10-23 18:29 ` [PATCH v2 2/4] network: don't allow connection to OWE AKM if disabled James Prestwood
2024-10-24 14:02   ` Denis Kenzior [this message]
2024-10-23 18:29 ` [PATCH v2 3/4] network: fix OWE transition BSS selection James Prestwood
2024-10-23 18:29 ` [PATCH v2 4/4] auto-t: add test for the new OweDisable driver quirk James Prestwood

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=f10961fd-0839-4f65-a772-c7c850f00844@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    /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