From: ludo@gnu.org (Ludovic Courtès)
To: 28869@debbugs.gnu.org
Subject: [bug#28869] [PATCH] gnu: wpa-supplicant: Fix "KRACK" key reinstallation attacks [security fixes].
Date: Tue, 17 Oct 2017 22:13:27 +0200 [thread overview]
Message-ID: <877evt1qjc.fsf@gnu.org> (raw)
In-Reply-To: <20171016214910.GC20802@jasmine.lan> (Leo Famulari's message of "Mon, 16 Oct 2017 17:49:10 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Mon, Oct 16, 2017 at 11:23:28PM +0200, Marius Bakke wrote:
>> Leo Famulari <leo@famulari.name> writes:
>>
>> > Fixes CVE-2017-{13078,13079,13080,13081,13082,13087,13088}.
>> >
>> > See these announcements for more information:
>> > https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt
>> > https://www.krackattacks.com/
>> >
>> > * gnu/packages/patches/wpa-supplicant-CVE-2017-13082.patch,
>> > gnu/packages/patches/wpa-supplicant-fix-key-reuse.patch,
>> > gnu/packages/patches/wpa-supplicant-fix-nonce-reuse.patch
>> > gnu/packages/patches/wpa-supplicant-fix-zeroed-keys.patch,
>> > gnu/packages/patches/wpa-supplicant-krack-followups.patch: New files.
>> > * gnu/packages/admin.scm (wpa-supplicant-minimal)[source]: Use them.
>> > * gnu/local.mk (dist_patch_DATA): Add them.
>>
>> LGTM, thanks for taking care of this.
>
> Thanks for the review! Pushed as
> 09748a352729762dacb8e6171752aaa6d03df85d
Thanks a lot for the prompt fix as usual!
Ludo’.
prev parent reply other threads:[~2017-10-17 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 18:20 [bug#28869] [PATCH] gnu: wpa-supplicant: Fix "KRACK" key reinstallation attacks [security fixes] Leo Famulari
2017-10-16 18:31 ` [bug#28869] gnu: wpa-supplicant: Fix "KRACK" key re-installation " Leo Famulari
2017-10-16 21:23 ` [bug#28869] [PATCH] gnu: wpa-supplicant: Fix "KRACK" key reinstallation " Marius Bakke
2017-10-16 21:49 ` bug#28869: " Leo Famulari
2017-10-17 20:13 ` Ludovic Courtès [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=877evt1qjc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28869@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.