From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Friends don't let friends run factory firmware
Date: Tue, 18 Feb 2014 17:13:56 -0500 [thread overview]
Message-ID: <CAA93jw6k=P74xAmRQ7e4=gnvxawUPSi8AFJh9H6awusv4Kt5zw@mail.gmail.com> (raw)
In-Reply-To: <A69AAC4A-8BF2-4792-8B41-55642F44933E@gmail.com>
While we are at it. (wobbly wednesday)
http://www.ioactive.com/news-events/IOActive_advisory_belkinwemo_2014.html
Don't leave home with it on.
At least they left the signing keys for the certificate in the
firmware, so that bad guys can exploit it, and good guys, improve it.
On Tue, Feb 18, 2014 at 5:10 PM, Rich Brown <richb.hanover@gmail.com> wrote:
> More excitement...
>
> https://isc.sans.edu/forums/diary/Linksys+Worm+TheMoon+Summary+What+we+know+so+far/17633
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-02-18 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 22:10 Rich Brown
2014-02-18 22:13 ` Dave Taht [this message]
2014-02-18 22:21 ` Dave Taht
2014-02-18 22:43 ` dpreed
-- strict thread matches above, loose matches on Subject: below --
2019-02-04 20:41 [Cerowrt-devel] friends " Dave Taht
2019-02-05 21:06 ` David P. Reed
2014-01-12 15:23 [Cerowrt-devel] Friends " Rich Brown
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='CAA93jw6k=P74xAmRQ7e4=gnvxawUPSi8AFJh9H6awusv4Kt5zw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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