From: Aaron Wood <woody77@gmail.com>
To: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Jonathan Morton" <chromatix99@gmail.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] anyone fiddlng with these?
Date: Thu, 15 Feb 2018 08:03:53 -0800 [thread overview]
Message-ID: <CALQXh-NxnHFhXpSGimD5vgL3yxCNCSxcXCUyqtrEuqm--8TKdQ@mail.gmail.com> (raw)
In-Reply-To: <16135.1518709300@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
"securely sending messages to the web" -> "Sending telemetry data to my
cloud-based data processing pipeline".
Both MQTT (over TLS) and HTTPS are both used heavily for sending data
upstream. Some companies in this space are thinking about security,
others... less so.
In general, the cloud providers for MQTT (Google Cloud IoT Core, AWS Cloud
IoT, etc) are taking it very seriously. The device platform suppliers are
starting to come around to the notion that having private keys in the
hardware is a ReallyGoodThing(tm). Companies like Maxim are making
hardware keys for making it easier to build devices that can do stronger
authentication to the cloud systems that they talk to:
http://www.microchip.com/design-centers/security-ics/cryptoauthentication/cloud-authentication/google-iot-core-atecc608a
My own view, having been around industrial automation, building controls,
and interactive home security for >20 years is that the residential market
is a small slice of IoT. Industrial and commercial uses are much, much
larger (and have a longer history, it just hasn't been called IoT).
(off soapbox)
On Thu, Feb 15, 2018 at 7:41 AM, <valdis.kletnieks@vt.edu> wrote:
> On Thu, 15 Feb 2018 14:52:49 +0100, Toke Høiland-Jørgensen said:
>
> > How else would you make sure your toothbrush phoned home to the
> > mothership?
> >
> > https://gizmodo.com/the-house-that-spied-on-me-1822429852
>
> Unless the mothership is the RPi3 sitting under my TV, I probably don't
> *want* it phoning home.
>
> And yes, I'm willing to pay extra for a toothbrush or light bulb or Roomba
> that
> can't be monetized because it only talks to a mothership that I control.
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
[-- Attachment #2: Type: text/html, Size: 3137 bytes --]
next prev parent reply other threads:[~2018-02-15 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:46 dpreed
2018-02-15 13:51 ` Jonathan Morton
2018-02-15 13:52 ` Toke Høiland-Jørgensen
2018-02-15 15:41 ` valdis.kletnieks
2018-02-15 16:03 ` Aaron Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 6:15 Dave Taht
2018-02-14 10:24 ` Toke Høiland-Jørgensen
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=CALQXh-NxnHFhXpSGimD5vgL3yxCNCSxcXCUyqtrEuqm--8TKdQ@mail.gmail.com \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=toke@toke.dk \
--cc=valdis.kletnieks@vt.edu \
/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