From: Alexander Holler <holler@ahsoftware.de>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Jon Nettleton <jon.nettleton@gmail.com>
Subject: Re: [PATCH 1/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only
Date: Fri, 07 Nov 2014 15:40:48 +0100 [thread overview]
Message-ID: <545CD9F0.50207@ahsoftware.de> (raw)
In-Reply-To: <CAP9ODKqtw0_KHLs40hUk53R3ipeSJ=vx1cQCw471_fW74DcZ3Q@mail.gmail.com>
Am 07.11.2014 um 12:34 schrieb Otavio Salvador:
> On Fri, Nov 7, 2014 at 7:43 AM, Alexander Holler <holler@ahsoftware.de> wrote:
>> Nothing in userspace should be able to kill the HW.
>> Not even just as root and for sure not that easy.
>>
>> For obvious reason, I haven't tested this patch thoroughly.
>>
>> Reported-by: Jon Nettleton <jon.nettleton@gmail.com>
>> Signed-off-by: Alexander Holler <holler@ahsoftware.de>
>
> I have a mix of feelings about the patch.
>
> Long story, short:
>
> - We ought to have a FSL_OTP_WRITE_SUPPORT config option
>
> The writing support is specially useful for manufacturing images where
> we can use Linux to do the initial programing, consult a database to
> find out inventory information (MAC address for example) and do proper
> programing on the OTP fuses. However I also believe we shouldn't have
> this available on regular kernel images as it is easy to get a
> 'expensive paper weight'.
>
> So would you be keen to rework the patch and include a write support
> config option?
No.
Sorry but I really think such dangerous stuff never should make it's way
into any kernel which doesn't have big red and yellow signs attached to
it. And unfortunately that isn't possible.
And even if it would be possible to mark kernels as dangerous, I think
that functionality should only be part of a bootloader where it isn't
reachable by normal userspace.
Regards,
Alexander Holler
next prev parent reply other threads:[~2014-11-07 14:48 UTC|newest]
Thread overview: 26+ 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 [this message]
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
2014-11-09 19:20 ` Nikolay Dimitrov
2014-11-07 16:03 ` Eric Bénard
2014-11-07 15:50 ` Eric Bénard
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=545CD9F0.50207@ahsoftware.de \
--to=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.