From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Michael Yartys <michael.yartys@protonmail.com>,
Michael Yartys via Make-wifi-fast
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] New Wi-Fi vulnerabilities
Date: Tue, 11 May 2021 21:18:37 +0200 [thread overview]
Message-ID: <877dk5nkoi.fsf@toke.dk> (raw)
In-Reply-To: <KjEgSYhigaI26216G1Fx_xT3Nh_gD-NMBTRdTN_SVyGJwXu2LnOiNVa9VB9rHF95dSmI9jpQ8eWE92uX7ECU08ZVQBN30HDwZ-vsRQrn108=@protonmail.com>
Michael Yartys via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net>
writes:
> Hi
>
> Hot off the press! Mathy Vanhoef has uncovered new Wi-Fi exploits:
> https://www.fragattacks.com/
>
> Not exactly trivial to exploit, but probably interesting to this list
> as it involves fragmentation and aggregation.
Patches were merged into the upstream kernel today as well:
https://lore.kernel.org/linux-wireless/20210511184454.164893-1-johannes@sipsolutions.net/T/
-Toke
next prev parent reply other threads:[~2021-05-11 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 18:47 Michael Yartys
2021-05-11 19:18 ` Toke Høiland-Jørgensen [this message]
2021-05-11 19:47 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dk5nkoi.fsf@toke.dk \
--to=toke@toke.dk \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michael.yartys@protonmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox