From: Dave Taht <dave.taht@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Dave Taht <dave@taht.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Hmmm... Worth reading re router security
Date: Sun, 16 Dec 2018 16:55:02 -0800 [thread overview]
Message-ID: <CAA93jw7FLk2Qk=hOwYz_qzo3_iiOpECeV+DPnB_a_ntJ_3dexQ@mail.gmail.com> (raw)
In-Reply-To: <1545007270.738911348@apps.rackspace.com>
Why is it so hard for a group like this to ALSO take a hard look at openwrt?
I don't recall what compiler was used for 18.06, but my kernel is 4.14
at least....
friends don't let friends run factory firmware. All that said, I have
no idea if present-day, prior-day openwrt currently addresses all the
concerns in this report, and I forwarded it to the openwrt-devel list.
I'd tried to get ahold of mudge and co dozens of times in the last 7
years. Glad they finally paid attention.
On Sun, Dec 16, 2018 at 4:41 PM David P. Reed <dpreed@deepplum.com> wrote:
>
> A look at home routers, and a surprising bug in Linux/MIPS - https://cyber-itl.org/2018/12/07/a-look-at-home-routers-and-linux-mips.html
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next prev parent reply other threads:[~2018-12-17 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 0:41 David P. Reed
2018-12-17 0:55 ` Dave Taht [this message]
2018-12-17 3:02 ` 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='CAA93jw7FLk2Qk=hOwYz_qzo3_iiOpECeV+DPnB_a_ntJ_3dexQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=dpreed@deepplum.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