Re: Crash on malformed archive

2022-11-17 Thread Julien Voisin
Indeed, I can't reproduce the issue locally on the git version. I'll let you know should I find any new ones :) On Fri, 4 Nov 2022 at 06:59, Paul Eggert wrote: > On 2022-11-01 10:51, Julien Voisin wrote: > > Unfortunately, compiling from the current git repo doesn't work, make it > > exiting wit

Re: Crash on malformed archive

2022-11-03 Thread Paul Eggert
On 2022-11-01 10:51, Julien Voisin wrote: Unfortunately, compiling from the current git repo doesn't work, make it exiting with `clang: error: no such file or directory: './parse-datetime.c'. You need Bison to build from Git. I installed the attached patch to mention this and fix a few other R

Re: Crash on malformed archive

2022-11-01 Thread Julien Voisin
Unfortunately, compiling from the current git repo doesn't work, make it exiting with `clang: error: no such file or directory: './parse-datetime.c'. Also, yes, I was talking about the tar_checksum() [src/list.c] check. We're currently working internally to be able to fuzz binaries at scale, so o

Re: Crash on malformed archive

2022-10-29 Thread Christian Schoenebeck
On Thursday, October 27, 2022 10:29:57 PM CEST Paul Eggert wrote: > > The reproducer is attached, and you may want to remove the checksum check > > from tar to reproduce the crash locally. > > Sorry, I don't know what is meant by "remove the checksum check". I > didn't do that, whatever it is. I

Re: Crash on malformed archive

2022-10-27 Thread Paul Eggert
Thanks for the report. Unfortunately I'm not seeing the crash here. I'm running on Ubuntu 22.10 x86-64, and built tar 1.34 from source with: ./configure make CFLAGS='-g3 -O2 -fsanitize=address' Here's my failed attempt to reproduce the bug: $ mkdir d $ cd d $ ../src/tar -G -g -S --ac