ubject: [50 character or so descriptive subject here (for reference)]
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-re
On Tue, Oct 31, 2017 at 3:53 PM, Clark Wang wrote:
> On Tue, Oct 31, 2017 at 3:25 PM, Clark Wang wrote:
>
>> On Mon, Oct 30, 2017 at 10:41 PM, Chet Ramey wrote:
>>
>>>
>>> This is an effect of using single quotes in the @Q operator. If you want
>>> to single-quote a string containing single quo
On Mon, Oct 30, 2017 at 8:35 PM, Greg Wooledge wrote:
>
> What's the bug? They are equivalent.
>
It's not a bad thing if we can make the language a bit more elegant unless
the cost is not worth it.
>
> If you mean "I would like bash to perform a second optimization pass
> over the result of ${
For now the `declare' command is under SHELL BUILTIN COMMANDS in the man
page so people may think bash parses the command line parameters the same
way as other built-in commands which is not true.
[STEP 100] # echo $BASH_VERSION
4.4.12(4)-release
[STEP 101] # declare -a arr=()
[STEP 102] #
On 11/7/17 9:56 AM, Alex Nichols wrote:
> Thank you for taking the time to respond to my email.
> I accept that this is likely not a security issue outside of being a social
> engineering attack, but the buggy behaviour that i'm curious about is that
> in each case the allocation should only have
On 11/7/17 6:58 AM, Alex Nichols wrote:
> Hi All,
>
>
> I’m an Ethical Hacking student at Coventry university and while doing some
> exploit development on my Linux boxes I stumbled across a bug in the bash
> 4.4.12(1) - release.
As others have explained, this is not a bug, nor is it any kind of
Thank you for taking the time to respond to my email.
I accept that this is likely not a security issue outside of being a social
engineering attack, but the buggy behaviour that i'm curious about is that
in each case the allocation should only have been of 2147483647 bytes in
size (the size of th
On Tue, Nov 7, 2017 at 5:58 AM, Alex Nichols wrote:
[...]
> In order to trigger the bug I executed the command *`*cat sploit.buf*`*
> where sploit.buf is a just over 2GB file of ‘A’ characters. When this
> command is executed the bash terminal crashes with the following error
> “Bash: xrealloc: ..
On Tue, Nov 07, 2017 at 11:58:40AM +, Alex Nichols wrote:
> In order to trigger the bug I executed the command *`*cat sploit.buf*`*
> This bug may present a potential security risk as a malicious user may be
> able to crash a users bash session by tricking them into executing a
> malicious bas
Hi All,
I’m an Ethical Hacking student at Coventry university and while doing some
exploit development on my Linux boxes I stumbled across a bug in the bash
4.4.12(1) - release.
In order to trigger the bug I executed the command *`*cat sploit.buf*`*
where sploit.buf is a just over 2GB file of ‘
10 matches
Mail list logo
