Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] side issue, related to the bigger picture surrounding Cerowrt and Bufferbloat.
Date: Sat, 25 Jan 2014 22:04:41 -0500 (EST)	[thread overview]
Message-ID: <1390705481.041814229@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw7kwqGs2cATRD7XiXzke30kbUxBN4=ZU+uzdsuP3e3yxA@mail.gmail.com>

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


On Friday, January 24, 2014 5:27pm, "Dave Taht" <dave.taht@gmail.com> said:
 

> and also, suddenly every device with a web server on it on 80 and 443
> is vulnerable, ranging from your printer to your fridge.
 
One of the reasons I like the "Cerowrt project" is that it focuses on fixing the aspects of the Internet plumbing that are due to careless practices like presuming that a printer or fridge will be protected inside a "firewall" and thus need not be designed correctly.
 
It reminds me of the attitude toward safety taken by the Auto Industry prior to Ralph Nader.  (whether you like Nader or not, his point was correct at the time - GM and Ford engineering did not design sufficiently safe cars, and that had a huge social impact that individuals could not cope with).
 
We now have printers and fridges that are "unsafe at any speed", just as we have access networks that are knowingly designed to get bloated under stress, amplifying the stress rather than ameliorating it.
 
Now there may be "temporary kludges" that can protect the printers and fridges thus misdesigned - and NAT firewalls are possibly OK in that light.  But honestly, I want to be able to connect to my printer from anywhere.
 
For a few bucks I can probably build a front-end box for my printer that is a printer server based on encrypted connections (using SSL with certificates, perhaps). E.g. for each printer and fridge, a Raspberry Pi with a USB WiFi interface, connected directly on IPv6. That's about $50 per badly designed consumer electronics device.
 
I'd prefer, however for the printer makers, etc. to make this a standard.  To do so, we need an open source project like Cerowrt to show the way, perhaps starting with the front-end box that implements the standard, since adding software to a printer or fridge itself is hard.
 
 

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

  parent reply	other threads:[~2014-01-26  3:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 20:59 [Cerowrt-devel] Comcast specific Cerowrt-3.10.26-7: another "too exciting for me" unrelease Dave Taht
2014-01-24 17:06 ` Dave Taht
2014-01-24 22:08   ` Toke Høiland-Jørgensen
2014-01-24 22:27     ` Dave Taht
2014-01-24 23:14       ` Sebastian Moeller
2014-01-26  3:04       ` dpreed [this message]
2014-01-25 16:57   ` Jim Reisert AD1C
2014-01-25 17:09     ` Dave Taht
2014-01-25 17:14       ` 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=1390705481.041814229@apps.rackspace.com \
    --to=dpreed@reed.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