Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14448
| From | Pierre Gaston <pierre.gaston@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: bash brace issues (similar to shellshock) |
| Date | 2018-08-06 19:13 +0300 |
| Message-ID | <mailman.4756.1533572045.1292.bug-bash@gnu.org> (permalink) |
| References | <CAGF5XnnB0KTsAT1ioi2=LACiqz7dwUYKe5n5aBnJGZjFf+ZD_w@mail.gmail.com> |
On Mon, Aug 6, 2018 at 4:32 PM, martins dada <martinsdada03@gmail.com>
wrote:
> Find attached details regarding bash brace issues. King regards.
>
you are simply assigning (){ to a temporary environment before running the
command
$ n=(){ bash -c 'echo $n'
(){
just like:
a=foo bash -c 'echo $a'
I'd agree that I would not expect bash to accept this without quotes,
but it does not allow to execute arbitrary commands like shellshock did.
At least your examples don't show this.
Your third example is best understood if you move the redirection at the
end:
n=(){ a= date >\ echo
redirection can appear anywhere around the command
As your wrote it, it looks funny but it's not different from "date > file"
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: bash brace issues (similar to shellshock) Pierre Gaston <pierre.gaston@gmail.com> - 2018-08-06 19:13 +0300
csiph-web