➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author epicfaace
Recipients Arfrever, Daniel.Garcia, Jeffrey.Kintscher, Philippe.Godbout, benjamin.peterson, christian.heimes, edulix, epicfaace, georg.brandl, jcea, jwilk, lars.gustaebel, martin.panter, ned.deily, serhiy.storchaka, shanxS, taleinat, uhei3nn9
Date 2019-08-13.16:40:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565714424.59.0.0290002983747.issue21109@roundup.psfhosted.org>
In-reply-to
Content 
SafeTarFile does not pass the existing tests, mainly because the existing file Lib/test/tarfiletestdata/testtar.tar seems to be "unsafe", producing errors like these:

tarfile.SecurityError: <TarInfo 'ustar/blktype' at 0x7fb9119b3bb0>: block device

tarfile.SecurityError: <TarInfo 'ustar/regtype' at 0x7fb9119b3910>: duplicate name

It seems like the solution here is to remove block devices and duplicate names from testtar.tar. However, is this desirable -- do we need to keep these in for the tests for TarFile?
History
Date User Action Args
2019-08-13 16:40:24epicfaacesetrecipients: + epicfaace, georg.brandl, jcea, lars.gustaebel, taleinat, christian.heimes, benjamin.peterson, jwilk, ned.deily, Arfrever, martin.panter, serhiy.storchaka, edulix, Daniel.Garcia, Philippe.Godbout, shanxS, uhei3nn9, Jeffrey.Kintscher
2019-08-13 16:40:24epicfaacesetmessageid: <1565714424.59.0.0290002983747.issue21109@roundup.psfhosted.org>
2019-08-13 16:40:24epicfaacelinkissue21109 messages
2019-08-13 16:40:24epicfaacecreate