Re: history separates >| and 2>&1 tokens when recalled with !*

2016-04-22 Thread Chet Ramey
On 4/22/16 5:24 AM, Piotr Grzybowski wrote: > Hi, > > It is a history_tokenize_word problem, please consider the following: Yes, that's a good fix. There's an uncomfortable amount of knowledge of shell syntax in that function. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chauce

Re: Scripts passed into "-c" with an embedded newline won't execute trap if last command fails

2016-04-22 Thread Chet Ramey
On 4/21/16 12:48 PM, Brian Vandenberg wrote: > Description: > > I ran into this issue while experimenting with gnu make and .ONESHELL. > I've boiled the issue down to the following simple example: > > $ newline=$'\n' > $ bash -e -c "trap 'echo handler' INT ERR;/bin/true; sleep 2; > ${newline}/b

Re: completion-prefix-display-length doesn't check for common prefix

2016-04-22 Thread Chet Ramey
On 4/21/16 2:42 PM, Grisha Levit wrote: > f() { COMPREPLY=(aa bb cc); } > complete -F f f > bind 'set completion-prefix-display-length 2' > > $ f [TAB][TAB] > ...aa ...bb ...cc > > None of the completion entries share a common pre

Re: Bug in syntax checking causes unintended running of a function

2016-04-22 Thread Chet Ramey
On 4/21/16 3:40 AM, dnade@orange.com wrote: > I think the shellshock mitigations have blocked the injection from happening. > > Do you think these should/could be applied to all function definitions? That's what the posix-mode behavior of abandoning the entire script does. -- ``The lyf so

Re: Possibly Bash explot

2016-04-22 Thread Nikolay Kolev
Well, you never know. It crashes consistently - I will try to create a reproducible code snippet for you. On Fri, Apr 22, 2016 at 8:06 AM, Chet Ramey wrote: > On 4/21/16 7:12 PM, Nikolay Kolev wrote: > > Basically, after doing a bunch of unset -f, I can crash Bash, version GNU > > bash, version

Re: Possibly Bash explot

2016-04-22 Thread Chet Ramey
On 4/21/16 7:12 PM, Nikolay Kolev wrote: > Basically, after doing a bunch of unset -f, I can crash Bash, version GNU > bash, version 4.3.42(1)-release (x86_64-apple-darwin15.0.0), which could > possibly be an attack vector. Here's the info from /var/log/system.log It's unlikely that this is an exp

Re: compgen -A arrayvar does not include associative arrays

2016-04-22 Thread Chet Ramey
On 4/21/16 3:21 PM, Grisha Levit wrote: > $ echo ${BASH_CMDS@a}; compgen -A arrayvar BASH_CMDS; echo $? > A > 1 > > The description doesn't specify that the output is limited to indexed > arrays only and it would be nice to have associative array variables > included as well. I will add something

Re: history separates >| and 2>&1 tokens when recalled with !*

2016-04-22 Thread Piotr Grzybowski
Hi, It is a history_tokenize_word problem, please consider the following: diff --git a/lib/readline/histexpand.c b/lib/readline/histexpand.c index fdecebc..ca4b4c8 100644 --- a/lib/readline/histexpand.c +++ b/lib/readline/histexpand.c @@ -1447,7 +1447,8 @@ history_tokenize_word (string, ind)

Re: history separates >| and 2>&1 tokens when recalled with !*

2016-04-22 Thread Piotr Grzybowski
hi, yes, this happens here: lib/readline/histexpand.c:1406 result[offset++] = ' '; pg On 22 Apr 2016, at 01:28, idal...@home.idallen.ca wrote: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFL

Re: Possibly Bash explot

2016-04-22 Thread Piotr Grzybowski
hi, I cannot replicate this in anyway, I just created 1024 functions and then ran unset -f in a while [ 1 ]; do done; loop on the very same bash version but on earlier version of darwin, and everything seems fine. Could you please provide the exact code that triggers the problem, together wit