From: valdis.kletnieks@vt.edu
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Sebastian Moeller <moeller0@gmx.de>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] security guidelines for home routers
Date: Tue, 27 Nov 2018 13:23:51 -0500 [thread overview]
Message-ID: <33485.1543343031@turing-police.cc.vt.edu> (raw)
In-Reply-To: <alpine.DEB.2.20.1811271156340.7766@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
On Tue, 27 Nov 2018 12:03:35 +0100, Mikael Abrahamsson said:
> I'd really like to see a wider audience weigh in on the pro:s and con:s of
> this approach. Do parents really want to come home to their 12 year old
> who might have opened up their residential gateway and installed something
> the 12 year old downloaded from the Internet? Perhaps yes, perhaps no.
That's a parenting problem not easily solved via technology. In particular, there's
the issue that often, the 12 year old is more clever than the parent - or the person
who designed the parental controls on the device.
On Tue, 27 Nov 2018 13:17:57 +0200, Jonathan Morton said:
> Currently, the easiest way to build a machine that's *truly* secure is to
> take something like a 6502 (which is still being manufactured by WDC) and
> associated 74AHC-series logic chips, SRAMs and EEPROMs, a 4-layer PCBs, all of
> which are built on crude enough technology to be physically examined for
> backdoor devices in an airport-grade X-ray machine if necessary. Then write
> the necessary software in assembly, which can be translated to machine code (or
> at least verified) by hand if you're truly paranoid, and toggle it in byte by
>byte on the front panel.
> Good luck getting a web browser running on one of those, though.
Couldn't find a browser, but somebody cooked up an ethernet based webserver for a 6502..
https://developers.slashdot.org/story/03/08/16/1226253/a-tcpip-stack-and-web-server-in-basic
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
next prev parent reply other threads:[~2018-11-27 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 18:05 Dave Taht
2018-11-26 18:24 ` Sebastian Moeller
2018-11-26 18:35 ` Mikael Abrahamsson
2018-11-26 22:13 ` Sebastian Moeller
2018-11-27 11:03 ` Mikael Abrahamsson
2018-11-27 11:52 ` Sebastian Moeller
2018-11-27 13:34 ` Mikael Abrahamsson
2018-11-28 13:49 ` Sebastian Moeller
2018-11-27 18:23 ` valdis.kletnieks [this message]
2018-11-26 18:40 ` Dave Taht
2018-11-26 21:05 ` Toke Høiland-Jørgensen
2018-11-26 22:28 ` Sebastian Moeller
2018-11-27 0:29 ` David P. Reed
2018-11-27 11:07 ` Mikael Abrahamsson
2018-11-27 11:17 ` Jonathan Morton
2018-11-28 9:17 ` Michael Richardson
2018-11-28 9:14 ` Michael Richardson
2018-11-28 19:10 ` David P. Reed
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=33485.1543343031@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=swmike@swm.pp.se \
/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