From: Nikolay Dimitrov <picmaster@mail.bg>
To: Alexander Holler <holler@ahsoftware.de>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Jon Nettleton <jon.nettleton@gmail.com>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only
Date: Sun, 09 Nov 2014 14:34:25 +0200 [thread overview]
Message-ID: <545F5F51.4050304@mail.bg> (raw)
In-Reply-To: <545E65D3.5080003@ahsoftware.de>
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.
To me it seems that the current state of affairs is already perfectly
OK and there's no need to panic.
Kind regards,
Nikolay
next prev parent reply other threads:[~2014-11-09 12:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 9:43 [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only Alexander Holler
2014-11-07 9:43 ` [PATCH 1/1] " Alexander Holler
2014-11-07 11:34 ` Otavio Salvador
2014-11-07 14:40 ` Alexander Holler
2014-11-07 15:06 ` Otavio Salvador
2014-11-07 15:26 ` Alexander Holler
2014-11-07 14:00 ` [PATCH 0/1] " Eric Bénard
2014-11-07 14:31 ` Jon Nettleton
2014-11-07 14:55 ` Alexander Holler
2014-11-07 15:04 ` Eric Bénard
2014-11-07 15:07 ` Otavio Salvador
2014-11-07 15:23 ` Alexander Holler
2014-11-07 16:00 ` Otavio Salvador
2014-11-07 16:38 ` Alexander Holler
2014-11-08 2:03 ` Nikolay Dimitrov
2014-11-08 8:58 ` Chris Tapp
2014-11-08 9:32 ` Jon Nettleton
2014-11-08 18:49 ` Alexander Holler
2014-11-09 10:14 ` Alexander Holler
2014-11-09 15:09 ` Eric Bénard
2014-11-09 17:03 ` Bob Cochran
2014-11-09 12:34 ` Nikolay Dimitrov [this message]
2014-11-09 18:09 ` Alexander Holler
2014-11-09 19:20 ` Nikolay Dimitrov
2014-11-07 16:03 ` Eric Bénard
2014-11-07 15:50 ` Eric Bénard
-- strict thread matches above, loose matches on Subject: below --
2014-11-08 21:54 Robin Findley
2014-11-10 14:11 ` Alexander Holler
2014-11-13 19:19 ` Alexander Holler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545F5F51.4050304@mail.bg \
--to=picmaster@mail.bg \
--cc=holler@ahsoftware.de \
--cc=jon.nettleton@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.