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 v4 1/4] network: add support for SAE password identifiers
Date: Fri, 15 Dec 2023 10:20:48 -0600	[thread overview]
Message-ID: <1af0dc61-137e-454d-87c5-4e02f766d504@gmail.com> (raw)
In-Reply-To: <20231214123400.12924-1-prestwoj@gmail.com>

Hi James,

On 12/14/23 06:33, James Prestwood wrote:
> Adds a new network profile setting [Security].PasswordIdentifier.
> When set (and the BSS enables SAE password identifiers) the network
> and handshake object will read this and use it for the SAE
> exchange.
> 
> Building the handshake will fail if:
>   - there is no password identifier set and the BSS sets the
>     "exclusive" bit.
>   - there is a password identifier set and the BSS does not set
>     the "in-use" bit.
> ---
>   src/network.c | 37 ++++++++++++++++++++++++++++++++++++-
>   1 file changed, 36 insertions(+), 1 deletion(-)
> 
> v4:
>   * Moved the checks out of network_load_psk and into the
>     handshake setup function. This is more consistent to where
>     other BSS-specific checks are made.
> 

All applied, thanks.

Regards,
-Denis


      parent reply	other threads:[~2023-12-15 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 12:33 [PATCH v4 1/4] network: add support for SAE password identifiers James Prestwood
2023-12-14 12:33 ` [PATCH v4 2/4] doc: document [Security].PasswordIdentifier James Prestwood
2023-12-14 12:33 ` [PATCH v4 3/4] auto-t: add H2E password identifier test James Prestwood
2023-12-14 12:34 ` [PATCH v4 4/4] auto-t: throw exception if executable is missing James Prestwood
2023-12-15 16:20 ` Denis Kenzior [this message]

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=1af0dc61-137e-454d-87c5-4e02f766d504@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