Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] security guidelines for home routers
Date: Tue, 27 Nov 2018 12:07:51 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1811271204250.7766@uplift.swm.pp.se> (raw)
In-Reply-To: <1543278579.232231705@apps.rackspace.com>

On Mon, 26 Nov 2018, David P. Reed 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 is that 99% of the 
population do not care about this, they just want to get their network 
running. That's why apple succeeds with their products, because they sell 
a "this is secure and works"-product, even if this security means you have 
to go to an authorized apple store to get your components replaced 
(because they're cryptographically paired for security reasons). It's 
possibly also that for most of Apples customers, this level of security is 
too high. People would rather have their pictures unencrypted and 
extractable without password from the device, compared to them being lost 
because the device was damanged otherwise broken.

So we need to come up with a security regime that makes sense for the most 
amount of people, and then try to still cater to the ones who want to do 
more/less.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2018-11-27 11:07 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 [this message]
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=alpine.DEB.2.20.1811271204250.7766@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.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