From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] anyone fiddlng with these?
Date: Thu, 15 Feb 2018 08:46:42 -0500 (EST) [thread overview]
Message-ID: <1518702402.737522502@mobile.rackspace.com> (raw)
This is one of things that is happening. Question is what would be the right approach? Mozilla also seems to be hacking away with little architectural thinking. Under the theory that you don't need a theory, just "good code".
What could go wrong?
How did we get Spectre in every processor implementation? Answer: processor architects all copied a flawed concept that speculation can easily undo observables. But security is often about exfiltration, not just "getting into kernel mode".
Where did the operational architecture for these InterNOT of Things devices come from? Band aid thinking. Patch on patch.
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Wed, Feb 14, 2018 at 1:15 am
To: cerowrt-devel@lists.bufferbloat.net
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] anyone fiddlng with these?
An esp32 coupled with an arm based 802.14 mcu, or an lte chip...
"With one line of code you'll be securely sending messages to the web."
what could go wrong?"
https://www.particle.io/mesh
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next reply other threads:[~2018-02-15 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:46 dpreed [this message]
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
-- 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=1518702402.737522502@mobile.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