From: Alexander Holler <holler@ahsoftware.de>
To: Nikolay Dimitrov <picmaster@mail.bg>
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 19:09:22 +0100 [thread overview]
Message-ID: <545FADD2.9090505@ahsoftware.de> (raw)
In-Reply-To: <545F5F51.4050304@mail.bg>
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
next prev parent reply other threads:[~2014-11-09 18:11 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
2014-11-09 18:09 ` Alexander Holler [this message]
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=545FADD2.9090505@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=jon.nettleton@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=picmaster@mail.bg \
/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.