On 8/29/22 12:28 PM, Kerin Millar wrote:
For extglob to be arbitrarily enabled in either context is unexpected (and
undesirable).
The conditional command behavior is compatible with ksh93, and has been
this way for nearly twenty years. It's documented to behave that way. One
would think
On 8/29/22 2:03 PM, tetsu...@scope-eye.net wrote:
On 2022-08-29 11:43, Chet Ramey wrote:
On 8/28/22 2:11 PM, Lawrence Velázquez wrote:
On Sun, Aug 28, 2022, at 9:24 AM, Yair Lenga wrote:
Wanted to get feedback about the following "extensions" to bash that will
make it easier to work with
On Wed, 31 Aug 2022 10:55:58 -0400
Chet Ramey wrote:
> On 8/29/22 12:28 PM, Kerin Millar wrote:
>
> >>> For extglob to be arbitrarily enabled in either context is unexpected
> >>> (and undesirable).
> >>
> >> The conditional command behavior is compatible with ksh93, and has been
> >> this way
Are you sure?
The patch i have attached fixes a buffer overflow if the xform is a
single character string.
31.08.2022, 22:26, "Chet Ramey" :
On 8/30/22 1:02 PM, Иван Капранов wrote:
Configuration Information [Automatically generated, do not
change]:
On 8/30/22 1:02 PM, Иван Капранов wrote:
Repeat-By:
1. Build bash with asan 2. Run with AFL++ crafted input (in attachment)
There's no attachment.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey,
On 8/30/22 1:05 PM, Иван Капранов wrote:
Bash Version: 5.1
Patch Level: 16
Release Status: release
Hi! I was fuzzing bash with AFL++ and found stack overflow.
Yes, if you word-expand a string that specifies that an identical word
expansion be performed, you're going to
On 8/31/22 3:34 PM, Ivan Kapranov wrote:
Are you sure?
The patch i have attached fixes a buffer overflow if the xform is a single
character string.
The xform is always a single-character string. xform[1] had better be the
'\0' that terminates it. If it's not, the xform is invalid. Nothing
On 8/30/22 1:02 PM, Иван Капранов wrote:
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall
Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto
-ffat-lto-objects -fstack-protector-strong -Wformat
-Werror=format-security -Wall
uname output: Linux koltir-Default-string
On 8/31/22 3:58 PM, Евгений Штанов wrote:
Bash Version: 5.1
Patch Level: 16
Release Status: release
Description:
Hi! I was fuzzing bash with AFL++ and found segmentation fault.
Backtrace in in attachment
You have created an infinite loop sourcing the same file and run
If you want some more interesting seg faults, here are some:
1)
bash-5.1$ (\${_@P};${_@P})
Segmentation fault (core dumped)
# golfed version of p='${p@P}'; : "${p@P}"
bash-5.1$ bash --norc
bash-5.1$ PS1=\${PS1@P}
Segmentation fault (core dumped)
bash-5.1$
# in an
I am on vacation and just skimmed this long thread so I might have
missed some of the context but I wanted throw out that I recently wrote
a loadable plugin that among other things, can convert JSON to and from
bash arrays.
Anyone interested can check it out at these git repos.
On Wed, 2022-08-31 at 11:11 -0400, Chet Ramey wrote:
> On 8/29/22 2:03 PM, tetsu...@scope-eye.net wrote:
>
> > It would also help
> > greatly if the shell could internally handle hierarchical data in
> > variables.
>
> That's a fundamental change. There would have to be a better reason
> to make
13 matches
Mail list logo
