From: Etienne Champetier <champetier.etienne@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Matt Taggart <matt@lackof.org>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] OTA exploitable wifi bugs
Date: Thu, 13 Oct 2022 15:03:35 -0400 [thread overview]
Message-ID: <CAOdf3gp9TfEVRS4StqOqZg-PzgTjfZSHYxj6sE6yssRzg65vPw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6MgSNgmiJya1CGXUuZcS0P71uUjJPV4OEiC1QVO_Pq2w@mail.gmail.com>
Fixes already commited by Felix Fietkau in master and 22.03
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=26f400210d6b3780fcc0deb89b9741837df9c8b8
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=f1de43d0a045a154c74281bc60bf1c44c990071b
Le jeu. 13 oct. 2022 à 13:14, Dave Taht via Cerowrt-devel
<cerowrt-devel@lists.bufferbloat.net> a écrit :
>
> yuck. 0 days suck. Why couldn't they have sat on this for a while?
>
> On Thu, Oct 13, 2022 at 9:59 AM Matt Taggart via Cerowrt-devel
> <cerowrt-devel@lists.bufferbloat.net> wrote:
> >
> > https://www.openwall.com/lists/oss-security/2022/10/13/2
> >
> > Presumably openwrt and other router firmwares (FOSS and proprietary)
> > will be effected?
> > Also android and maybe TVs, etc? That's a whole lot of devices.
> >
> > Lots of updating in our futures... maybe this will help get newer SQM
> > rolled out more (but maybe not enabled by default).
> >
> > Sorry, this is probably my fault, I just updated a bunch of stuff last
> > night (after I washed my car causing it to rain).
> >
> > --
> > Matt Taggart
> > matt@lackof.org
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> This song goes out to all the folk that thought Stadia would work:
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2022-10-13 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 16:59 Matt Taggart
2022-10-13 17:14 ` Dave Taht
2022-10-13 19:03 ` Etienne Champetier [this message]
2022-10-13 19:05 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOdf3gp9TfEVRS4StqOqZg-PzgTjfZSHYxj6sE6yssRzg65vPw@mail.gmail.com \
--to=champetier.etienne@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=matt@lackof.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox