wpa-supplicant: Align to recipe from Scarthgap

[floion]

We add the recipe with the patches from Scarthgap revision 97f732ce9b914ea4022c9425611c16d333c2787b

This is the same package version but adds additional CVE patches.

Change-type: patch

---

Contributor checklist

• Changes have been tested
  • Covered in automated test suite
  • Manual test case recorded
• Change-type present on at least one commit
• Signed-off-by is present
• The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[flowzone-app]

Website deployed to CF Pages, 👀 preview link https://f30b1cab.balena-os.pages.dev

[ycardaillac]

@floion this is a complete back port from the scarthgap recipe right?
if so @balena-os/balena-os-team do we have a mechanism in place to keep track with the recipes we back port from mainstream?
Do we back port those recipe so that we have a more or less homogeneous network stack between device types and yocto versions?
It is simple simple enough for wpa supplicant, but the exercise seems a bit more complex for network manager:

./meta-resin-pyro/recipes-connectivity/networkmanager/networkmanager_1.32.12.bbappend
./meta-resin-pyro/recipes-connectivity/networkmanager/networkmanager_1.32.12.bb
./meta-resin-rocko/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-balena-common/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-balena-common/recipes-connectivity/networkmanager/networkmanager_1.46.0.bb
./meta-balena-thud/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-balena-warrior/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-resin-sumo/recipes-connectivity/networkmanager/networkmanager_1.32.12.bbappend
./meta-resin-sumo/recipes-connectivity/networkmanager/networkmanager_1.32.12.bb

How is all of that supposed to work together? what's the general idea here?

[floion]

@floion this is a complete back port from the scarthgap recipe right? if so @balena-os/balena-os-team do we have a mechanism in place to keep track with the recipes we back port from mainstream? Do we back port those recipe so that we have a more or less homogeneous network stack between device types and yocto versions? It is simple simple enough for wpa supplicant, but the exercise seems a bit more complex for network manager:

./meta-resin-pyro/recipes-connectivity/networkmanager/networkmanager_1.32.12.bbappend
./meta-resin-pyro/recipes-connectivity/networkmanager/networkmanager_1.32.12.bb
./meta-resin-rocko/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-balena-common/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-balena-common/recipes-connectivity/networkmanager/networkmanager_1.46.0.bb
./meta-balena-thud/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-balena-warrior/recipes-connectivity/networkmanager/networkmanager_%.bbappend
./meta-resin-sumo/recipes-connectivity/networkmanager/networkmanager_1.32.12.bbappend
./meta-resin-sumo/recipes-connectivity/networkmanager/networkmanager_1.32.12.bb

How is all of that supposed to work together? what's the general idea here?

Hi @ycardaillac yes it's the same recipe and patches from the Scarthgap revision I pointed to.
Yes, what we place in meta-balena-common is intended to be used by all the supported boards so we are homogeneous across all of them.
It should be simple for all these packages we keep common for all device types because pyro, rocko, sumo should not be used anymore by any of our devices types (these are old and deprecated Yocto releases we don't really support anymore)

As for how we keep track, maybe we should standardize and keep all the versions of these packages (which usually we try to have at latest stable versions) in this file like we do for some of them: https://github.com/balena-os/meta-balena/blob/master/meta-balena-common/conf/distro/include/balena-os.inc#L124
Or we can offload all of these to a new file we add in meta-balena-common named like https://github.com/balena-os/meta-balena/blob/master/meta-balena-common/conf/distro/include/balena-os.inc#L3