Re: Bash security issue

[Nick Bowler]

On 2014-09-25 15:08 -0700, Linda Walsh wrote:
> Eric Blake wrote:
> > Where I'm coming from is that in portable shell programming, you _can't_
> > assign a value to f()=...  The fact that portable programs are now
> > slammed with the notion that some values cannot be portably assigned
> > to a variable...
> ---
> slammed?  It's not like this is new...
[...]
> As other have said:
> 
>     «Geir Hauge wrote: Bash has had this feature since "forever"»
> 
>     «Pierre Gaston wrote:  How many instance have you found since the
>      introduction of this feature more than 20 years ago?»

Since I don't use bash it's not surprising that I've never noticed any
problem.

But I try to write scripts that are portable to bash, because I know
that many people do use it.  What I learned from this is that bog-
standard assignments like this:

   foo=$1; export foo

are not portable to bash, and may fail to work correctly depending on
the user's input.

Cheers,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)