From: Dave Taht <dave.taht@gmail.com>
To: David P Reed <dpreed@reed.com>
Cc: Rich Brown <richb.hanover@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] dnsmasq CVEs
Date: Wed, 4 Oct 2017 09:38:10 -0700 [thread overview]
Message-ID: <CAA93jw7ZDwv8yFFOBuxUP8bp-K+3tQ9Xj9inHYHt3thMkKZw2A@mail.gmail.com> (raw)
In-Reply-To: <82be7dac-c30b-449d-a392-305c31b83519@reed.com>
well, I still think the system is rotten to its (cpu) cores and much
better hardware support for security is needed to start from in order
to have better software. Multics pioneered a few things in that
department as I recall, but research mostly died in the 90s...
Blatant Plug: The mill cpu folk are giving a talk about how they do
secure interprocess communication tonight in san jose, ca. I'm going.
While I expect to be cheered up by the design (the underlying
architecture supports memory protections down to the byte, not page,
level, and may be largely immune to ROP) - I expect to be depressed by
how far away they still remain from building the darn thing.
https://millcomputing.com/event/inter-process-communication-talk-on-october-4-2017/
next prev parent reply other threads:[~2017-10-04 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 0:43 Rich Brown
2017-10-04 3:49 ` Dave Taht
2017-10-04 13:12 ` David P Reed
2017-10-04 16:38 ` Dave Taht [this message]
2017-10-07 13:33 ` dpreed
2017-10-07 20:54 ` dpreed
[not found] ` <59d8d7ae.5b37c80a.9c70e.c057SMTPIN_ADDED_BROKEN@mx.google.com>
2017-10-07 18:32 ` Dave Taht
2017-10-07 20:28 ` Dave Taht
[not found] ` <59d8d7b6.06c3370a.2a6e1.858eSMTPIN_ADDED_BROKEN@mx.google.com>
2017-10-07 20:42 ` valdis.kletnieks
2017-10-09 8:32 ` Mikael Abrahamsson
2017-10-09 17:33 ` Dave Taht
2017-10-09 18:37 ` dpreed
-- strict thread matches above, loose matches on Subject: below --
2017-10-02 18:18 [Cerowrt-devel] dnsmasq cves 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=CAA93jw7ZDwv8yFFOBuxUP8bp-K+3tQ9Xj9inHYHt3thMkKZw2A@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
--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