On 6/7/22 15:49, Chet Ramey wrote:
> On 6/7/22 7:57 AM, Gergely wrote:
>
>>> Because you haven't forced bash to write outside its own address space or
>>> corrupt another area on the stack. This is a resource exhaustion issue,
>>> no more.
>>
>> I did force it to write out of bounds, hence the seg
On 6/7/22 7:57 AM, Gergely wrote:
>> Because you haven't forced bash to write outside its own address space or
>> corrupt another area on the stack. This is a resource exhaustion issue,
>> no more.
>
>
> I did force it to write out of bounds, hence the segfault.
That's backwards. You got a SIGS
On 6/6/22 16:14, Chet Ramey wrote:
> On 6/2/22 4:00 PM, Gergely wrote:
>
>> I could not produce a scenario in 15 minutes that would indicate that
>> this corrupts other sections, as there is a considerable gap between the
>> stack and everything else. This is OS-dependent though and bash has no
>>
