Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] friends don't let friends run factory firmware
Date: Tue, 5 Feb 2019 16:06:46 -0500 (EST)	[thread overview]
Message-ID: <1549400806.789924737@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6H4PSOnWODE9=xTOkV7NXvXoz668F0jpxNjw8KOjcEWQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]


Well, pots and kettles - I bet there are, amongst the huge numbers of LEDE/OpenWRt packages, some very useful DDoS amplification concerns. So it's really not a strong proof of the claim that "factory firmware" is bad.

My own home border router I built myself, and yet it acquires new problems with new updates (as well as having some fixed).

And, one thing that scares the bejeezus out of me is the passion for stuff like code allowing injection of binary code into the kernel (eBPF) being thrown into the Linux Kernel for "performance reasons". Hacking the clever network developer has never been easier - just throw them some complicated and subtle code that runs in the kernel that "everybody thinks is the coolest new thing". Here's the description of eBPF from the documentation I use: "The extended BPF (eBPF) variant has become a universal in-kernel virtual machine, that has hooks all over the kernel. " Lovely. So userspace can make the kernel do completely untestable things.
 
There are lots of great things about creating the freedom to experiment, modify your own devices' firmware, etc. I think the existence of that community makes the world generally safer (more eyeballs, more innovation, etc.).
 
But this idea that everybody benefits by running some non-standard firmware they choose for themselves?  That's bizarre to me, unjustifiable by any very good argument.
 
UBNT here seems to be doing the right thing - developing an update and distributing it to all its customers.

-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Monday, February 4, 2019 3:41pm
To: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] friends don't let friends run factory firmware

https://www.zdnet.com/article/over-485000-ubiquiti-devices-vulnerable-to-new-attack/

-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

[-- Attachment #2: Type: text/html, Size: 2961 bytes --]

  reply	other threads:[~2019-02-05 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 20:41 Dave Taht
2019-02-05 21:06 ` David P. Reed [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-18 22:10 [Cerowrt-devel] Friends " Rich Brown
2014-02-18 22:13 ` Dave Taht
2014-02-18 22:21   ` Dave Taht
2014-02-18 22:43     ` dpreed
2014-01-12 15:23 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=1549400806.789924737@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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