[issue41316] tarfile: Do not write full path in FNAME field

2020-10-21 Thread Inada Naoki
Change by Inada Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker ___

[issue41316] tarfile: Do not write full path in FNAME field

2020-10-20 Thread miss-islington
miss-islington added the comment: New changeset e866f33a48ee24e447fafd181f0da5f9584e0340 by Miss Skeleton (bot) in branch '3.8': bpo-41316: Make tarfile follow specs for FNAME (GH-21511) https://github.com/python/cpython/commit/e866f33a48ee24e447fafd181f0da5f9584e0340 --

[issue41316] tarfile: Do not write full path in FNAME field

2020-10-20 Thread miss-islington
miss-islington added the comment: New changeset 7917170c5b4793ca9443f753aaecb8fbb3ad54ef by Miss Skeleton (bot) in branch '3.9': bpo-41316: Make tarfile follow specs for FNAME (GH-21511) https://github.com/python/cpython/commit/7917170c5b4793ca9443f753aaecb8fbb3ad54ef --

[issue41316] tarfile: Do not write full path in FNAME field

2020-09-07 Thread miss-islington
Change by miss-islington : -- pull_requests: +21225 pull_request: https://github.com/python/cpython/pull/22141 ___ Python tracker ___

[issue41316] tarfile: Do not write full path in FNAME field

2020-09-07 Thread miss-islington
miss-islington added the comment: New changeset 22748a83d927d3da1beaed771be30887c42b2500 by Artem Bulgakov in branch 'master': bpo-41316: Make tarfile follow specs for FNAME (GH-21511) https://github.com/python/cpython/commit/22748a83d927d3da1beaed771be30887c42b2500 -- nosy:

[issue41316] tarfile: Do not write full path in FNAME field

2020-09-07 Thread miss-islington
Change by miss-islington : -- pull_requests: +21224 pull_request: https://github.com/python/cpython/pull/22140 ___ Python tracker ___

[issue41316] tarfile: Do not write full path in FNAME field

2020-07-17 Thread Artem Bulgakov
Artem Bulgakov added the comment: Hi. My PR doesn't remove the possibility to add tree into tar file. It only fixes header for GZIP compression. Any data after this header is not affected. You can test it by creating two archives with the same data but one with my patch and the second

[issue41316] tarfile: Do not write full path in FNAME field

2020-07-17 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41316] tarfile: Do not write full path in FNAME field

2020-07-16 Thread Emmanuel Arias
Emmanuel Arias added the comment: Hi, If I understand correctly, the name that you are using into the tar is the basename of the file. I didn't test it yet, but this PR will remove the possibility to create a file into the tar using the source tree folder? Maybe we can think about implement

[issue41316] tarfile: Do not write full path in FNAME field

2020-07-16 Thread Artem Bulgakov
Change by Artem Bulgakov : -- keywords: +patch pull_requests: +20646 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21511 ___ Python tracker ___

[issue41316] tarfile: Do not write full path in FNAME field

2020-07-16 Thread Artem Bulgakov
New submission from Artem Bulgakov : tarfile sets FNAME field to the path given by user: Lib/tarfile.py:424 It writes full path instead of just basename if user specified absolute path. Some archive viewer apps like 7-Zip may process file incorrectly. Also it creates security issue because