[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54366135.50301@oracle.com>
Date: Thu, 09 Oct 2014 11:19:33 +0100
From: John Haxby <john.haxby@...cle.com>
To: oss-security@...ts.openwall.com
Subject: Re: Thoughts on Shellshock and beyond
On 09/10/14 00:53, Tim wrote:
> Well, I think we can all think of a few options, some more portable
> than others. The current namespace change is one option, obviously,
> but one might go a different route with more time to design it
> initially. Other ideas:
>
> 1) A single dedicated environment variable for all function exports.
> e.g.:
>
> BASH_FUNCTIONS='f() { ... }
> g() { ... }
> ...
> '
You don't need export -f for that either and you don't need anything
special in the child: just do «eval "$BASH_FUNCTIONS"» which also has
the benefit of making it quite plain that you're living dangerously.
jch
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
