On 5/9/17 12:41 AM, Eduardo Bustamante wrote:
> On Mon, May 8, 2017 at 3:09 PM, Chet Ramey wrote:
>> There's no compelling reason to disallow it. If a system administrator
>> wants to unbind certain readline commands (and unset INPUTRC!) to protect
>> against a specific use case, he is free to do
On 5/8/17 2:33 PM, Eduardo Bustamante wrote:
> This doesn't seem to be related to the other read memory corruption
> issues, since it doesn't crash normal read/read -r.
Nope, it's the same.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis''
dualbus@debian:~/bash-fuzzing/read-readline$ base64 loop
AAAbLbUA9loQGDIYLhwYGBkYGJgYGBj4FwAYYBlEAERLG0YK
dualbus@debian:~/bash-fuzzing/read-readline$ od -c loop
000 \0 \0 033 - 265 \0 366 Z 020 030 2 030 . 034 030 030
020 031 030 030 230 030 030 030 370 027 \0 030 ` 031 D
On Mon, May 08, 2017 at 07:43:27PM -0400, Chet Ramey wrote:
> If you want a workaround that should work in bash-4.2 and bash-4.3, try
> using some large number (people have used ) for HISTSIZE, giving you
> effectively unlimited history.
Or check $BASH_VERSION (or ${BASH_VERSINFO[@]}) before d
