From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 2118BE008BA; Sun, 9 Nov 2014 10:11:31 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.ahsoftware.de (h1446028.stratoserver.net [85.214.92.142]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3F2A7E007C0 for ; Sun, 9 Nov 2014 10:11:28 -0800 (PST) Received: by mail.ahsoftware.de (Postfix, from userid 65534) id 94BC52C9C205; Sun, 9 Nov 2014 19:11:25 +0100 (CET) Received: from eiche.ahsoftware (p4FC37686.dip0.t-ipconnect.de [79.195.118.134]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ahsoftware.de (Postfix) with ESMTPSA id F2C9B2C9C1FE for ; Sun, 9 Nov 2014 19:11:24 +0100 (CET) Received: by eiche.ahsoftware (Postfix, from userid 65534) id 29B028E2D8; Sun, 9 Nov 2014 19:11:24 +0100 (CET) Received: from krabat.ahsoftware (unknown [IPv6:feee::5246:5dff:fe8b:95f8]) by eiche.ahsoftware (Postfix) with ESMTP id 7272A8E2D8; Sun, 9 Nov 2014 18:09:23 +0000 (UTC) Message-ID: <545FADD2.9090505@ahsoftware.de> Date: Sun, 09 Nov 2014 19:09:22 +0100 From: Alexander Holler User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Nikolay Dimitrov References: <1415353415-3805-1-git-send-email-holler@ahsoftware.de> <20141107150003.27c16356@e6520eb.localdomain> <20141107160443.765f9b19@e6520eb.localdomain> <545CE3DE.4070902@ahsoftware.de> <545CF576.5050403@ahsoftware.de> <545D79DC.8030701@mail.bg> <545E65D3.5080003@ahsoftware.de> <545F5F51.4050304@mail.bg> In-Reply-To: <545F5F51.4050304@mail.bg> Cc: "meta-freescale@yoctoproject.org" , Jon Nettleton , Otavio Salvador Subject: Re: [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2014 18:11:31 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Am 09.11.2014 13:34, schrieb Nikolay Dimitrov: > Hi Alexander, > > The eFuses are lockable. If you don't intend to further modify their > value after proper programming, you should lock them. If you don't do > so, you shouldn't blame the Linux driver for the consequences. > > Crippling the IMX OTP driver doesn't solve the system security issues. > I can write to the IMX physical memory (e.g. to program OCOTP > registers) without this Linux driver at all, I just need proper > privileges and the devregs tool (thanks Eric & Troy!). > > I have just like you some imx6 hobby boards. If one of them is bricked, > it's totally my fault. And yet we have hundreds of thousands of imx6 > boards on the road, which we locked during manufacturing, and disabled > the OTP driver, so it's impossible to brick them via OTP. First let me quote again the sentence from the reference manual you missed to quote: "In order to avoid "rogue" code performing erroneous writes to OTP, a special unlocking sequence is required for writes to the fuse banks." To conclude, you are saying: - The (easy) write functionalty of the driver should be kept because it's of no use on locked devices anyway. - Unlocked devices ("hobby boards", whatever that is) are second class devices where it's the owners fault if some malware, wrong script, typo or similiar writes to some file in the sysfs. - The way to write to the OTP offered by the driver is the same as the way offered by the HW, which means the more complicated way implemented in the HW (which, by the way, is still in effect when using devregs) is senseless. ... > To me it seems that the current state of affairs is already perfectly > OK and there's no need to panic. So revealing and trying to fix bugs nowadays means panicking? I thought it's still part of the normal software development process. Maybe I really have become oldschool and better get a towel. Anyway, as I'm running out of hope and polite arguments (at least in regard to this topic) and getting near to the point of using sentences Linus has unfortunately become famous for, I better stop to comment further. Alexander Holler