Dear Simon,
In message
<20211018121315.v8.4.Ie78bfbfca0d01d9cba501e127f446ec48e1f7afe@changeid> you
wrote:
>
> The environment variables should be of the form "var=value". Values can
> extend to multiple lines. See the README under 'Environment Variables:'
> for more information and an example. Note that environment variables may
> not end in +
This makes not really clear that the restriction is on the name (and
not the value) of the environment variable.
> but can start with other strange characters, including
> underscore, comma and slash.
I would omit this as it does not provide any relevant information
here, and in addition it is misleading as it could be interpreted
that such characters are only legal at the start of the variable
name. But you can do:
=> setenv .-^-. foo
=> printenv .-^-.
.-^-.=foo
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
A secure program has to be robust: it must be able to deal with
conditions that "can't happen", whether user input, program error or
library/etc. This is basic damage control. Buffer overflow errors
have nothing to do with security, but everything with stupidity.
-- Wietse Venema in <5cnqm3$8...@spike.porcupine.org>
