All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov via buildroot <buildroot@buildroot.org>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/2] package/wpa_supplicant: bump version to 2.10
Date: Mon, 31 Jan 2022 22:32:45 +0100	[thread overview]
Message-ID: <CAGm1_ku=iCDJZqDpDPoQAnF7YwtCtKdo3OZbdyb8yJ6Wv5wRXA@mail.gmail.com> (raw)
In-Reply-To: <YfhIzDNP6sIsaG7J@curiosity>

On Mon, Jan 31, 2022 at 9:38 PM Sergey Matyukevich <geomatsi@gmail.com> wrote:
>
> Hello Yegor,
>
> > Hi Sergey,
> >
> > On Mon, Jan 31, 2022 at 8:48 PM Sergey Matyukevich <geomatsi@gmail.com> wrote:
> > >
> > > Update wpa_supplicant to the latest release v2.10. Drop all the patches
> > > as they have already been upstreamed. Remove from .mk file all the
> > > WPA_SUPPLICANT_IGNORE_CVES records since those CVEs will not be
> > > reported against the new version.
> > >
> > > Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
>
> ...
>
> > Have you tried to build wpa_supplicant without
> > BR2_PACKAGE_WPA_SUPPLICANT_WPA3 and enabled
> > BR2_PACKAGE_WPA_SUPPLICANT_MESH_NETWORKING? I've got a linking error.
> > I have also sent a quick and dirty patch to the hostap mailing list
> > [1] but still got no answer.
> >
> > [1] http://lists.infradead.org/pipermail/hostap/2022-January/040181.html
>
> So far I have not observed that problem. I think we can handle it
> independently from the revision update, adding fixup patches if needed.
>
> I tried to reproduce it using the following wpa_supplicant configuration:
>
> BR2_PACKAGE_WPA_SUPPLICANT=y
> BR2_PACKAGE_WPA_SUPPLICANT_NL80211=y
> BR2_PACKAGE_WPA_SUPPLICANT_AP_SUPPORT=y
> BR2_PACKAGE_WPA_SUPPLICANT_MESH_NETWORKING=y
>
> However build succeeded. Could you please post your wpa_supplicant
> configuration snippet ? Probably the root cause is in openssl and some
> of its features need to be enabled in package/wpa_supplicant/Config.in.

I have pinned it down:

BR2_PACKAGE_WPA_SUPPLICANT=y
BR2_PACKAGE_WPA_SUPPLICANT_NL80211=y
BR2_PACKAGE_WPA_SUPPLICANT_AP_SUPPORT=y
BR2_PACKAGE_WPA_SUPPLICANT_MESH_NETWORKING=y
BR2_PACKAGE_WPA_SUPPLICANT_EAP=y

It is BR2_PACKAGE_WPA_SUPPLICANT_EAP option the selects NEED_SHA384.

Regards,
Yegor
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-31 21:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 19:48 [Buildroot] [PATCH 1/2] package/wpa_supplicant: bump version to 2.10 Sergey Matyukevich
2022-01-31 19:48 ` [Buildroot] [PATCH 2/2] package/hostapd: " Sergey Matyukevich
2022-02-01 17:22   ` Yegor Yefremov via buildroot
2022-01-31 20:14 ` [Buildroot] [PATCH 1/2] package/wpa_supplicant: " Yegor Yefremov via buildroot
2022-01-31 20:38   ` Sergey Matyukevich
2022-01-31 21:32     ` Yegor Yefremov via buildroot [this message]
2022-02-01  8:53       ` Sergey Matyukevich
2022-02-01 10:25         ` Yegor Yefremov via buildroot
2022-02-01 10:46           ` Sergey Matyukevich
2022-02-01 17:22 ` Yegor Yefremov via buildroot
2022-02-12 13:45 ` Arnout Vandecappelle

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='CAGm1_ku=iCDJZqDpDPoQAnF7YwtCtKdo3OZbdyb8yJ6Wv5wRXA@mail.gmail.com' \
    --to=buildroot@buildroot.org \
    --cc=geomatsi@gmail.com \
    --cc=matthew.weber@collins.com \
    --cc=yegorslists@googlemail.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.