[issue1531] tarfile.open(fileobj=f) and bad metadata of the first file within the archive

George Notaras added the comment: Thanks for the quick fix and the workaround. You are right about position 756. I hadn't spent enough time studying the ''ustar'' format. __ Tracker <[EMAIL PROTECTED]> __

[issue1531] tarfile.open(fileobj=f) and bad metadata of the first file within the archive

Lars Gustäbel added the comment: I fixed this in the trunk (r59260) and release25-maint branch (r59261). Thanks for the report. If you cannot wait for the next release, I recommend you use mode "r|" as a workaround. BTW, 756 is absolutely no realistic example value for the position of the second

[issue1531] tarfile.open(fileobj=f) and bad metadata of the first file within the archive

Changes by Lars Gustäbel: -- assignee: -> lars.gustaebel nosy: +lars.gustaebel __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing l

[issue1531] tarfile.open(fileobj=f) and bad metadata of the first file within the archive

New submission from George Notaras: Assume the following situation: - a healthy and uncompressed tar file: a.tar - the metadata of the 1st and second files within the archive start at positions 0 and 756 (realistic example values) I partially damage 200 bytes of metadata (byte range 0-500) of th