Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] security guidelines for home routers
Date: Tue, 27 Nov 2018 14:34:21 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1811271429340.7766@uplift.swm.pp.se> (raw)
In-Reply-To: <611D46EC-4E08-4D66-9163-C200FA2ECA09@gmx.de>

On Tue, 27 Nov 2018, Sebastian Moeller wrote:

> 	Really, which ones? I would like to know so I can avoid them ;) 
> Just joking, but I have never heard of secure booting in the context of 
> MIPS based routers and at least in the retail market most cheap devices 
> still seem MIPS based. Then again this is slowly changing with x86 (via 
> DOCSIS-SoCs and even the high end lantiq/intel dsl SoCs) and ARM slowly 
> seeping into the market. I think bot x86 and ARM have specs for secure 
> booting or related methods.

DTs Speedports.

> 	I am old school, once somebody has physical access to the device 
> it is game over already. Point in case people have found ways to decrypt 
> the encrypted configuration files huawei tends to use in their routers, 
> and some people even hacked docsis-modems. From my reading of the BSI 
> recommendations, even pressing a reset button long enough would be okay, 
> the only nono seems to be allowing changing the firmware to non-signed 
> ones without explicit opt-in by the user.

Again, how do you define "explicit opt-in"? Yes, cutting a wire inside the 
device is probably a good way to do it, if someone doesn't understand this 
is modification of the device then I don't know what is.

> 	But that is okay for a device that an ISP owns and rents out, but 
> decidedly not okay for a device I want to own.

I agree, but it might be exactly what some other people want to own, who 
just want things to work. There are plenty of devices that people pay and 
own, but they expect their ISP to manage and software update.

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

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