[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file

Jeffrey Kintscher added the comment: I recommend closing this issue since the behavior is the same as the BSD and GNU tar utilities. -- type: -> behavior ___ Python tracker

[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file

Jeffrey Kintscher added the comment: I did some testing with BSD and GNU tar to compare with Python's behavior. jfoo:~ jeff$ tar --version bsdtar 2.8.3 - libarchive 2.8.3 jeff@albarino:~$ tar --version tar (GNU tar) 1.28 Both BSD tar and GNU tar can create an empty tar file that consists of

[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file

Read Hughes added the comment: GNU description of tar file format: http://www.gnu.org/software/tar/manual/html_node/Standard.html Particular quotes that are relevant: >Physically, an archive consists of a series of file entries terminated by an >end-of-archive entry, which consists of two

[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file

Change by Eitan Adler : -- nosy: +eitan.adler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file

Change by Carl Harris : -- nosy: +hitbox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file

Change by Karthikeyan Singaravelan : -- nosy: +lars.gustaebel, serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing

[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file

New submission from Chris Siebenmann : The easiest reproduction of this is: import tarfile tarfile.open("/dev/zero", "r:") (If you use plain "r" you get a hang in attempted lzma decoding.) I believe this is probably due to a missing 'elif self.offset == 0:' in the 'except