From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 173C13CB35 for ; Tue, 27 Nov 2018 08:34:23 -0500 (EST) Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9093EB1; Tue, 27 Nov 2018 14:34:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1543325661; bh=ZB+eeEV3LhDXYsVXVQian09+Z5QzsqgzEfLUSmfIEXE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=IWM5dp0Prf3j166t3ZR3Ugn9SY3C0kYfH+JdOmyozvhVEjU7L/yjalO/Kxu1+441t WVyrq2KurNZ0gehG6KEQwFQAJk/1E4UKieaEn3/Qnmkb+AxzMSms0CDubZMn4yFPfx IJexOXuRLw7q7l+mYICXLW5x5ji3lI3r4vxAZ7Hk= Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8E4B19F; Tue, 27 Nov 2018 14:34:21 +0100 (CET) Date: Tue, 27 Nov 2018 14:34:21 +0100 (CET) From: Mikael Abrahamsson To: Sebastian Moeller cc: cerowrt-devel In-Reply-To: <611D46EC-4E08-4D66-9163-C200FA2ECA09@gmx.de> Message-ID: References: <6F8CDBFF-8B8A-4B6B-BCE9-918A69354626@gmx.de> <05A88D6B-51BC-4CC5-98D9-E85AE11D96AC@gmx.de> <611D46EC-4E08-4D66-9163-C200FA2ECA09@gmx.de> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) Organization: People's Front Against WWW MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Re: [Cerowrt-devel] security guidelines for home routers X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2018 13:34:23 -0000 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