Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11141] New: WF111 package no longer availabe
Date: Wed, 04 Jul 2018 14:29:44 +0000	[thread overview]
Message-ID: <bug-11141-163@https.bugs.busybox.net/> (raw)

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.

             reply	other threads:[~2018-07-04 14:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04 14:29 bugzilla at busybox.net [this message]
2018-07-10  9:43 ` [Buildroot] [Bug 11141] WF111 package no longer availabe bugzilla at busybox.net
2018-07-10  9:57 ` bugzilla at busybox.net
2018-07-10 10:21 ` bugzilla at busybox.net
2018-07-10 10:25 ` bugzilla at busybox.net
2018-07-10 16:38 ` bugzilla at busybox.net
2018-08-29 20:10 ` bugzilla at busybox.net

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=bug-11141-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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