Hello,
when rc is invoked, rc reconstructs shell variable and shell functions using
files in /env/.
in case of shell functions, rc evaluates whole data in the file.
this feature makes problem if the content is
fn foo {…}; maliciouscommand
I think this problem must be fixed.
Kenji Arisawa
2014/09/27 23:40、Christian Neukirchen <[email protected]> のメール：
>
> The problem could be completely avoided if the '{}' were implicit, that
> is, store
>
> fn foo { echo bar }
>
> as
>
> fn#foo=echo bar
>
> (Also, I heard Research Unix v8 sh(1) stored functions in the environment
> as "foo(){ ... }", i.e. without =. So this never clashes with any
> variable. Not sure if that works portably enough for plan9port, though.)
>
> --
> Christian Neukirchen <[email protected]> http://chneukirchen.org
>
>
