Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "David P. Reed" <dpreed@deepplum.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] security guidelines for home routers
Date: Wed, 28 Nov 2018 09:17:16 -0000	[thread overview]
Message-ID: <24484.1543396636@dooku.sandelman.ca> (raw)
In-Reply-To: <alpine.DEB.2.20.1811271204250.7766@uplift.swm.pp.se>

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]


Mikael Abrahamsson <swmike@swm.pp.se> wrote:
    >> Personally, I think it's time to move "security" out of the military
    >> sector of government..

    > I think we need some kind of international cooperation body that
    > develops guidelines that vendors can then slap their "approved
    > by"-sticker on the box by complying to these guidelines. Problem here

There are multiple efforts:

I'm involved with this one: https://www.iotsecurityfoundation.org/best-practice-guidelines/
(and there are more documents in progress)

There are other efforts, and there are attempts to coordinate, and there is
interest in the testing labs (EULabs, UL, and others) in doing evaluations
with prices from $ to $$$$$.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2018-11-28  9:17 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
2018-11-27 11:07         ` Mikael Abrahamsson
2018-11-27 11:17           ` Jonathan Morton
2018-11-28  9:17           ` Michael Richardson [this message]
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=24484.1543396636@dooku.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --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