From: Peter Korsgaard <peter@korsgaard.com>
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: Sun, 05 Mar 2023 18:36:25 +0100 [thread overview]
Message-ID: <87356j85ie.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230223164747.1653580-1-geomatsi@gmail.com> (Sergey Matyukevich's message of "Thu, 23 Feb 2023 19:47:47 +0300")
>>>>> "Sergey" == Sergey Matyukevich <geomatsi@gmail.com> writes:
> 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>
Committed to 2022.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-03-05 17:36 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
2023-03-05 17:36 ` Peter Korsgaard [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=87356j85ie.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=geomatsi@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