From: "David P. Reed" <dpreed@deepplum.com>
To: "Sebastian Moeller" <moeller0@gmx.de>
Cc: "Dave Täht" <dave.taht@gmail.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] security guidelines for home routers
Date: Mon, 26 Nov 2018 19:29:39 -0500 (EST) [thread overview]
Message-ID: <1543278579.232231705@apps.rackspace.com> (raw)
In-Reply-To: <13EA268F-994D-45FF-A0B2-1CAF4C530B4F@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2239 bytes --]
> I would like it very much if my country attempted to get to something> similar as a requirement for FCC certification or import. Stronger> yes, would be nice, but there was> nothing horrible in here that I could see.
Dave T. - You may remember from when I helped get you in contact with the FCC regarding their attempt to rule against software updates of routers. Subsequent to that, I and others were brought into an ex parte discussion with the top policy people in the FCC regarding their role in supporting security reviews of routers and development of secure routers for WiFi. The FCC lawyers have asserted that they have no legal authority whatsoever in regard to assuring security of routers.
They haven't been interested in communications security at all, in all of my work with them over the last 20 years. Personally, I don't see Congress passing laws on router security, or for that matter, "Internet of Things" security. There is some thought that the Federal Trade Commission might have authority under "consumer protection" and "product safety" laws. But FTC is generally weak and uninterested in regulating most technologies.
One of the US's problems (which may have parallels in Europe) is that ALL responsibility for communications security in the USG resides in the NSA, which is in the Department of Defense. Every other part of the USG depends on NSA support. (Even the Federal Information Processing Standards for commercial encryption are vetted officially by NSA, because they are the only agency that has security competencies)
Is it a good thing to bring NSA into regulating the security of home routers or IoT? Technically, they and their contractors are very sharp on this. I've worked with them since I began work in computer security in my research group at MIT in 1973. (we did no classified research, but NSA was part of our support, and the chief scientist of the NSA shared an office with me when he visited us).
Personally, I think it's time to move "security" out of the military sector of government..
But maybe not in the FCC, which is in a weird part of the USG, with no budget for technical expertise at all. (Congress doesn't want them to have technical resources)
[-- Attachment #2: Type: text/html, Size: 7017 bytes --]
next prev parent reply other threads:[~2018-11-27 0:29 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
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 [this message]
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=1543278579.232231705@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=moeller0@gmx.de \
/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