From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wpa_supplicant: fix builds with missing sha384 hash functions
Date: Thu, 23 Feb 2023 23:43:21 +0100 [thread overview]
Message-ID: <20230223234321.427b3772@windsurf> (raw)
In-Reply-To: <20230223164747.1653580-1-geomatsi@gmail.com>
On Thu, 23 Feb 2023 19:47:47 +0300
Sergey Matyukevich <geomatsi@gmail.com> wrote:
> SAE, unlike OWE or DPP, does not explicitly enable support for sha384
> hash functions. Possible WPA3 build issue is masked, since all three
> SAE/OWE/DPP are included. However, there exist other configurations
> that enable only SAE. For instance, one such build configuration is
> wpa_supplicant AP mode with mesh support.
>
> This change adds upstream patch that includes sha384 and sha256 hash
> functions to builds with SAE support.
>
> Fixes: http://autobuild.buildroot.net/results/f349130985870f4a781cca56c3f551108f81aa3e/
>
> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
> ---
> ...384-512-KDF-for-SAE-if-SHA384-512-is.patch | 62 +++++++++++++++++++
> 1 file changed, 62 insertions(+)
> create mode 100644 package/wpa_supplicant/0003-Include-HMAC-SHA384-512-KDF-for-SAE-if-SHA384-512-is.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-23 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 16:47 [Buildroot] [PATCH 1/1] package/wpa_supplicant: fix builds with missing sha384 hash functions Sergey Matyukevich
2023-02-23 22:43 ` Thomas Petazzoni via buildroot [this message]
2023-03-05 17:36 ` Peter Korsgaard
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=20230223234321.427b3772@windsurf \
--to=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=thomas.petazzoni@bootlin.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 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.