From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap5: Allow use of a plain text env file
Date: Sat, 23 Mar 2013 01:23:51 +0100 [thread overview]
Message-ID: <20130323002351.B9D44200048@gemini.denx.de> (raw)
In-Reply-To: <1363992223-1628-1-git-send-email-nm@ti.com>
Dear Nishanth Menon,
In message <1363992223-1628-1-git-send-email-nm@ti.com> you wrote:
> For production systems it is better to use script images since
> they are protected by checksums and carry valuable information
> like name and timestamp. Also, you can't validate the content
> passed to env import.
>
> But for development, it is easier to use the env import command and
> plain text files instead of script-images.
Be careful here. There are some subtle, but important differences.
With a script image, you are basically running standard commands,
which includes certain tests and limitations. With "env import", you
are just importing a set of environment settings, without further
tests for permissions, etc.
For example, think if data like your MAC address or board serial
number are important to you, or if you are willing to have any user
overwrite these with arbitrary data.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I think that all right-thinking people in this country are sick and
tired of being told that ordinary decent people are fed up in this
country with being sick and tired. I'm certainly not. But I'm sick
and tired of being told that I am. - Monty Python
next prev parent reply other threads:[~2013-03-23 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 22:43 [U-Boot] [PATCH] omap5: Allow use of a plain text env file Nishanth Menon
2013-03-23 0:23 ` Wolfgang Denk [this message]
2013-03-23 1:07 ` Tom Rini
2013-03-23 1:03 ` Tom Rini
2013-03-23 15:27 ` Nishanth Menon
2013-03-24 4:20 ` Sricharan R
2013-03-25 2:39 ` Nishanth Menon
2013-03-25 4:46 ` Sricharan R
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=20130323002351.B9D44200048@gemini.denx.de \
--to=wd@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox