New: WF111 package no longer availabe

https://bugs.busybox.net/show_bug.cgi?id=11141

Bug ID: 11141
Summary: WF111 package no longer availabe
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned at buildroot.uclibc.org
Reporter: geert at my-clay.com
CC: buildroot at uclibc.org
Target Milestone: ---

The current WF111 version is 5-2-2-r3. It is no longer available on the download website. And therefore builds that rely on it are broken.

The latest WF111 version is 5-2-2-r4 and contains a fix for KRACK exploit and requires a patched WPA_SUPPLICANT version 2.6. The latest version is available.

This package is available for public download from the URL as specified in the WF111 make file.

This issue applies to buildroot version 2018.02 and newer, since the download URL was introduced there.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=11141

--- Comment #1 from Peter Korsgaard <[email protected]> --- Why are they broken? Buildroot should fall back to the copy we have on sources.buildroot.net:

https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r3-armv5te.tar.gz
Resolving www.silabs.com (www.silabs.com)... 23.53.20.107 Connecting to www.silabs.com (www.silabs.com)|23.53.20.107|:443... connected. HTTP request sent, awaiting response... 404 Not Found

2018-07-10 11:33:42 ERROR 404: Not Found.

--2018-07-10 11:33:42--
http://sources.buildroot.net/wf111/wf111-linux-driver-5-2-2-r3-armv5te.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.27.167.48, 104.27.166.48, 2400:cb00:2048:1::681b:a730, ...
Connecting to sources.buildroot.net (sources.buildroot.net)|104.27.167.48|:80... connected.
HTTP request sent, awaiting response... 404 Not Found

2018-07-10 11:33:43 ERROR 404: Not Found.

--2018-07-10 11:33:43--
http://sources.buildroot.net/wf111-linux-driver-5-2-2-r3-armv5te.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.27.167.48, 104.27.166.48, 2400:cb00:2048:1::681b:a730, ...
Connecting to sources.buildroot.net (sources.buildroot.net)|104.27.167.48|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2743425 (2.6M) [application/x-gtar-compressed]

With that said, updating to -4 is also fine. Do notice that they apparently haven't released a -4 x86 version:

wget
https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r4-x86.tar.gz
--2018-07-10 11:34:37--
https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r4-x86.tar.gz
Resolving www.silabs.com (www.silabs.com)... 23.53.20.107 Connecting to www.silabs.com (www.silabs.com)|23.53.20.107|:443... connected. HTTP request sent, awaiting response... 404 Not Found

What is this wpa-supplicant patch about? Is this something new for -4? Where can this patch be found?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=11141

--- Comment #2 from Geert <[email protected]> ---
Hello Peter,

First of all, thank you for your assistance. It is highly appreciated.

We are using the armv7-a variant, that is not availible on the Buildroot sources:
/usr/bin/make -j1 O=/home/geert/buildroot/output HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig
make[1]: Entering directory '/home/geert/buildroot'
make[1]: Leaving directory '/home/geert/buildroot'

PATH="/home/geert/buildroot/output/host/bin:/home/geert/buildroot/output/host/sbin:/home/geert/bin:/home/geert/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/path/to/the/directory" BR2_DL_DIR="/home/geert/buildroot/dl"
BUILD_DIR=/home/geert/buildroot/output/build O=/home/geert/buildroot/output
flock /home/geert/buildroot/dl/wf111/ support/download/dl-wrapper -c '5-2-2-r3'
-d '/home/geert/buildroot/dl/wf111' -D '/home/geert/buildroot/dl' -f
'wf111-linux-driver-5-2-2-r3-armv7-a.tar.gz' -H 'package/wf111//wf111.hash' -n
'wf111-5-2-2-r3' -N 'wf111' -o
'/home/geert/buildroot/dl/wf111/wf111-linux-driver-5-2-2-r3-armv7-a.tar.gz' -u
https+https://www.silabs.com/documents/login/software -u
http\|urlencode+http://sources.buildroot.net/wf111 -u
http\|urlencode+http://sources.buildroot.net --
--2018-07-10 11:50:50--
https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r3-armv7-a.tar.gz
Resolving www.silabs.com (www.silabs.com)... 172.227.80.68
Connecting to www.silabs.com (www.silabs.com)|172.227.80.68|:443... connected.
HTTP request sent, awaiting response... 404 Not Found

2018-07-10 11:50:50 ERROR 404: Not Found.

--2018-07-10 11:50:50--
http://sources.buildroot.net/wf111/wf111-linux-driver-5-2-2-r3-armv7-a.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.27.167.48, 104.27.166.48, 2400:cb00:2048:1::681b:a630, ...
Connecting to sources.buildroot.net (sources.buildroot.net)|104.27.167.48|:80... connected.
HTTP request sent, awaiting response... 404 Not Found

2018-07-10 11:50:51 ERROR 404: Not Found.

--2018-07-10 11:50:51--
http://sources.buildroot.net/wf111-linux-driver-5-2-2-r3-armv7-a.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.27.166.48, 104.27.167.48, 2400:cb00:2048:1::681b:a730, ...
Connecting to sources.buildroot.net (sources.buildroot.net)|104.27.166.48|:80... connected.
HTTP request sent, awaiting response... 404 Not Found

2018-07-10 11:50:51 ERROR 404: Not Found.

package/pkg-generic.mk:135: recipe for target '/home/geert/buildroot/output/build/wf111-5-2-2-r3/.stamp_downloaded' failed
make: *** [/home/geert/buildroot/output/build/wf111-5-2-2-r3/.stamp_downloaded] Error 1

Further more silabs makes a mess with these releases. You are right that they did not release a v4 for x86.

Having the mechanism to protect against ARP broadcast messages (from 5.2.2-v4) is a pre for us.

Note that they did not only update the version number, but also the format... from "wf111-linux-driver-5-2-2-r3-armv7-a.tar.gz"
to: "wf111-linux-driver_5.2.2-r4_armv7-a.tar.gz" (dots between version and 2x _)

There are the release notes from Silabs:
Changes: 5.2.2-r4 Compared to 5.2.2-r3
Date: May 21, 2018
Changes
? Added a mechanism to protect against a replayed ARP broadcast message. To protect against Key Reinstallation Attacks (KRACK)
in a 4-way handshake, it is required to use at least wpa_supplicant v2.6 with applied patches from https://w1.fi/security/2017-1/.
Limitations
? Same as in 5.2.2.
Known Issues
? Same as in 5.2.2.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=11141

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED

--- Comment #3 from Peter Korsgaard <[email protected]> --- Ahh, ok. The mirroring gets a bit confused with these architecture/variant specific tarballs. I had the tarball here locally, so I have copied it to sources.buildroot.net as well.

With that said, it would be great if you could send a patch to the mailing list bumping the version to -4 for the ARM variants. We already carry the needed wpa_supplicant patches.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=11141

--- Comment #4 from Geert <[email protected]> ---
Hello Peter,

Thanks for adding the package to the buildroot backup site.

I would love to create a patch.
How can I start: is there a manual that described how you can create patches? (and thus contributing to Buildroot)? And who's responsible for merging these into LTS released?

Kind regards,
Geert Visser

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=11141

--- Comment #5 from Peter Korsgaard <[email protected]> ---
You are welcome. Patches are created with git and sent to the mailing list. Have a look at the "submitting patches" section in the manual for the details of how to do so:

https://buildroot.org/downloads/manual/manual.html#submitting-patches

I maintain the LTS branch, so I will backport important patches to the branch once they have been applied to the master branch.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=11141

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #6 from Thomas Petazzoni <[email protected]> --- This problem has been fixed by:

(1) Adding the old tarballs in sources.buildroot.org (this is the fix for
2018.08)

(2) Updating the wf111 version used on ARM in commit
https://git.buildroot.org/buildroot/commit/package/wf111?h=next&id=1e80bd9ec64ff4065f72ab0d47d863e87bf0580c
(this is going to be in 2018.11)

Thanks for the initial bug report!

You are receiving this mail because:
You are on the CC list for the bug.