From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Disable command at runtime
Date: Fri, 29 Jul 2016 09:31:33 -0400 [thread overview]
Message-ID: <20160729133133.GL17970@bill-the-cat> (raw)
In-Reply-To: <1f085e1d-378c-5f29-2f35-988b8d110da8@elnico.cz>
On Thu, Jul 28, 2016 at 04:40:29AM -0700, kubiznak.petr wrote:
> Hello,
>
> I wonder whether it is possible to dynamically enable/disable a command.
> Since u-boot does not provide any secure authentication method, it is
> dangerous to keep some commands available to a potential hacker. E.g.
> the "fuse" command. On the other hand, I need these commands during the
> manufacturing process. So my idea is to enable/disable the commands
> dynamically based on some obscure logic. Is there a way to do it without
> need to deeply hack the code?
Well, there's a few ways to do this. The first way would simply be to
install a different build of U-Boot onto the board than the one used
during flashing as part of the manufacturing process.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160729/5fe0dbdb/attachment.sig>
next prev parent reply other threads:[~2016-07-29 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 11:40 [U-Boot] Disable command at runtime kubiznak.petr
2016-07-29 13:31 ` Tom Rini [this message]
2016-07-29 14:37 ` Petr Kubizňák
2016-07-29 14:59 ` Tom Rini
2016-07-29 15:57 ` Petr Kubizňák
2016-08-01 20:05 ` Wolfgang Denk
2016-08-02 6:57 ` Petr Kubizňák
2016-08-03 12:53 ` Wolfgang Denk
2016-08-01 20:38 ` Ladislav Michl
2016-08-02 7:11 ` Petr Kubizňák
2016-08-09 18:20 ` Simon Glass
2016-08-10 5:54 ` Petr Kubizňák
2016-08-01 19:59 ` Wolfgang Denk
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=20160729133133.GL17970@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.