bug#25041: Bugs in TAC and TAIL for closed stdin

2016-11-27 Thread Pádraig Brady
On 27/11/16 15:51, Jim Meyering wrote: > On Sun, Nov 27, 2016 at 7:40 AM, Pádraig Brady wrote: >> I'll push the attached later > > Thanks to both of you. > > That patch looks fine, modulo a formatting nit: the second line is > indented one space too far: > > + f->ignore = ! (reopen

bug#25041: Bugs in TAC and TAIL for closed stdin

2016-11-27 Thread Jim Meyering
On Sun, Nov 27, 2016 at 7:40 AM, Pádraig Brady wrote: > I'll push the attached later Thanks to both of you. That patch looks fine, modulo a formatting nit: the second line is indented one space too far: + f->ignore = ! (reopen_inaccessible_files + && fo

bug#25041: Bugs in TAC and TAIL for closed stdin

2016-11-27 Thread Pádraig Brady
I'll push the attached later thanks again, Pádraiag >From a31edf2aab384bfd33a6f0ab123d688939c4ddf6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A1draig=20Brady?= Date: Sun, 27 Nov 2016 13:00:35 + Subject: [PATCH 1/2] tail: fix uninitialized memory read when failing to read file MIME-Version

bug#25041: Bugs in TAC and TAIL for closed stdin

2016-11-27 Thread Pádraig Brady
On 27/11/16 09:15, Marcel Böhme wrote: > Dear all, > > During fuzzing, we found one use-after-free in tac and one > invalid-loading-of-value in tail. > Interestingly, these errors can be observed only when stdin is externally > closed but internally expected to be open. > > The bugs were found

bug#25041: Bugs in TAC and TAIL for closed stdin

2016-11-27 Thread Marcel Böhme
Dear all, During fuzzing, we found one use-after-free in tac and one invalid-loading-of-value in tail. Interestingly, these errors can be observed only when stdin is externally closed but internally expected to be open. The bugs were found by AFLFast, a fork of AFL. The bug in tac was also fou