Re: heap-use-after-free in GNU Bash 4.4.0
By the way, we actually found more than 10 (potentially) different errors (judging by their backtrace), but I didn't want to spam the list. What would be the best way to report them? Regards On Sat, Sep 10, 2016 at 7:52 PM, Chet Ramey wrote: > On 9/9/16 9:35 AM, Franco Costantini wrote: > > Hi, > > > > we recently found an invalid memory access parsing and executing fuzzed > > bash code in GNU Bash 4.4.0 (bash-20160826 snapshot, found in > > http://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id= > 79eedac429c5112ae65a430674de5e4be1cd5444). > > Thanks for the report. > > Chet > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~ > chet/ >
Re: heap-use-after-free in GNU Bash 4.4.0
On 9/12/16 10:30 AM, Franco Costantini wrote: > By the way, we actually found more than 10 (potentially) different errors > (judging by their backtrace), but I didn't want to spam the list. What > would be the best way to report them? Send them to me. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
[Bug] kill -l 0 outputs T, not EXIT
The command kill -l 0 outputs T. I would expect EXIT as T is not a valid signal or pseudosignal name. Since T is the last letter of EXIT, I suspect a typo somewhere. AT&T ksh93 outputs EXIT. pdksh/mksh and zsh output 0 (presumably EXIT is not a real signal). dash and yash give a "no such signal number" error. All of these seem sensible, but "T" does not. Confirmed in bash 2.05b.13, 3.2.57 and 4.4.0. Thanks, - M.
