tarfile
--- 讀取與寫入 tar 封存檔案¶
原始碼:Lib/tarfile.py
Thetarfile
module makes it possible to read and write tararchives, including those using gzip, bz2 and lzma compression.Use thezipfile
module to read or write.zip
files, or thehigher-level functions inshutil.
Some facts and figures:
reads and writes
gzip
,bz2
andlzma
compressed archivesif the respective modules are available.read/write support for the POSIX.1-1988 (ustar) format.
read/write support for the GNU tar format includinglongname andlonglinkextensions, read-only support for all variants of thesparse extensionincluding restoration of sparse files.
read/write support for the POSIX.1-2001 (pax) format.
handles directories, regular files, hardlinks, symbolic links, fifos,character devices and block devices and is able to acquire and restore fileinformation like timestamp, access permissions and owner.
在 3.3 版的變更:Added support forlzma
compression.
在 3.12 版的變更:Archives are extracted using afilter,which makes it possible to either limit surprising/dangerous features,or to acknowledge that they are expected and the archive is fully trusted.By default, archives are fully trusted, but this default is deprecatedand slated to change in Python 3.14.
- tarfile.open(name=None,mode='r',fileobj=None,bufsize=10240,**kwargs)¶
Return a
TarFile
object for the pathnamename. For detailedinformation onTarFile
objects and the keyword arguments that areallowed, seeTarFile 物件.mode has to be a string of the form
'filemode[:compression]'
, it defaultsto'r'
. Here is a full list of mode combinations:mode
action
'r'或'r:*'
Open for reading with transparentcompression (recommended).
'r:'
Open for reading exclusively withoutcompression.
'r:gz'
Open for reading with gzip compression.
'r:bz2'
Open for reading with bzip2 compression.
'r:xz'
Open for reading with lzma compression.
'x'
或'x:'
Create a tarfile exclusively withoutcompression.Raise a
FileExistsError
exceptionif it already exists.'x:gz'
Create a tarfile with gzip compression.Raise a
FileExistsError
exceptionif it already exists.'x:bz2'
Create a tarfile with bzip2 compression.Raise a
FileExistsError
exceptionif it already exists.'x:xz'
Create a tarfile with lzma compression.Raise a
FileExistsError
exceptionif it already exists.'a'或'a:'
Open for appending with no compression. Thefile is created if it does not exist.
'w'或'w:'
Open for uncompressed writing.
'w:gz'
Open for gzip compressed writing.
'w:bz2'
Open for bzip2 compressed writing.
'w:xz'
Open for lzma compressed writing.
Note that
'a:gz'
,'a:bz2'
or'a:xz'
is not possible. Ifmodeis not suitable to open a certain (compressed) file for reading,ReadError
is raised. Usemode'r'
to avoid this. If acompression method is not supported,CompressionError
is raised.Iffileobj is specified, it is used as an alternative to afile objectopened in binary mode forname. It is supposed to be at position 0.
For modes
'w:gz'
,'x:gz'
,'w|gz'
,'w:bz2'
,'x:bz2'
,'w|bz2'
,tarfile.open()
accepts the keyword argumentcompresslevel (default9
) to specify the compression level of the file.For modes
'w:xz'
and'x:xz'
,tarfile.open()
accepts thekeyword argumentpreset to specify the compression level of the file.For special purposes, there is a second format formode:
'filemode|[compression]'
.tarfile.open()
will return aTarFile
object that processes its data as a stream of blocks. No random seeking willbe done on the file. If given,fileobj may be any object that has aread()
orwrite()
method(depending on themode) that works with bytes.bufsize specifies the blocksize and defaults to20*512
bytes.Use this variant in combination with e.g.sys.stdin.buffer
, a socketfile object or a tape device.However, such aTarFile
object is limited in that it doesnot allow random access, see範例. The currentlypossible modes:Mode
Action
'r|*'
Open astream of tar blocks for readingwith transparent compression.
'r|'
Open astream of uncompressed tar blocksfor reading.
'r|gz'
Open a gzip compressedstream forreading.
'r|bz2'
Open a bzip2 compressedstream forreading.
'r|xz'
Open an lzma compressedstream forreading.
'w|'
Open an uncompressedstream for writing.
'w|gz'
Open a gzip compressedstream forwriting.
'w|bz2'
Open a bzip2 compressedstream forwriting.
'w|xz'
Open an lzma compressedstream forwriting.
在 3.5 版的變更:The
'x'
(exclusive creation) mode was added.在 3.6 版的變更:Thename parameter accepts apath-like object.
在 3.12 版的變更:Thecompresslevel keyword argument also works for streams.
- classtarfile.TarFile
Class for reading and writing tar archives. Do not use this class directly:use
tarfile.open()
instead. SeeTarFile 物件.
- tarfile.is_tarfile(name)¶
Return
True
ifname is a tar archive file, that thetarfile
module can read.name may be astr
, file, or file-like object.在 3.9 版的變更:Support for file and file-like objects.
Thetarfile
module defines the following exceptions:
- exceptiontarfile.ReadError¶
Is raised when a tar archive is opened, that either cannot be handled by the
tarfile
module or is somehow invalid.
- exceptiontarfile.CompressionError¶
Is raised when a compression method is not supported or when the data cannot bedecoded properly.
- exceptiontarfile.StreamError¶
Is raised for the limitations that are typical for stream-like
TarFile
objects.
- exceptiontarfile.ExtractError¶
Is raised fornon-fatal errors when using
TarFile.extract()
, but only ifTarFile.errorlevel
==2
.
- exceptiontarfile.HeaderError¶
Is raised by
TarInfo.frombuf()
if the buffer it gets is invalid.
- exceptiontarfile.AbsolutePathError¶
Raised to refuse extracting a member with an absolute path.
- exceptiontarfile.OutsideDestinationError¶
Raised to refuse extracting a member outside the destination directory.
- exceptiontarfile.SpecialFileError¶
Raised to refuse extracting a special file (e.g. a device or pipe).
- exceptiontarfile.AbsoluteLinkError¶
Raised to refuse extracting a symbolic link with an absolute path.
- exceptiontarfile.LinkOutsideDestinationError¶
Raised to refuse extracting a symbolic link pointing outside the destinationdirectory.
The following constants are available at the module level:
- tarfile.ENCODING¶
The default character encoding:
'utf-8'
on Windows, the value returned bysys.getfilesystemencoding()
otherwise.
Each of the following constants defines a tar archive format that thetarfile
module is able to create. See sectionSupported tar formats fordetails.
- tarfile.USTAR_FORMAT¶
POSIX.1-1988 (ustar) format.
- tarfile.GNU_FORMAT¶
GNU tar format.
- tarfile.PAX_FORMAT¶
POSIX.1-2001 (pax) format.
- tarfile.DEFAULT_FORMAT¶
The default format for creating archives. This is currently
PAX_FORMAT
.在 3.8 版的變更:The default format for new archives was changed to
PAX_FORMAT
fromGNU_FORMAT
.
也參考
zipfile
模組Documentation of the
zipfile
standard module.- Archiving operations
Documentation of the higher-level archiving facilities provided by thestandard
shutil
module.- GNU tar manual, Basic Tar Format
Documentation for tar archive files, including GNU tar extensions.
TarFile 物件¶
TheTarFile
object provides an interface to a tar archive. A tararchive is a sequence of blocks. An archive member (a stored file) is made up ofa header block followed by data blocks. It is possible to store a file in a tararchive several times. Each archive member is represented by aTarInfo
object, seeTarInfo 物件 for details.
ATarFile
object can be used as a context manager in awith
statement. It will automatically be closed when the block is completed. Pleasenote that in the event of an exception an archive opened for writing will notbe finalized; only the internally used file object will be closed. See the範例 section for a use case.
在 3.2 版被加入:Added support for the context management protocol.
- classtarfile.TarFile(name=None,mode='r',fileobj=None,format=DEFAULT_FORMAT,tarinfo=TarInfo,dereference=False,ignore_zeros=False,encoding=ENCODING,errors='surrogateescape',pax_headers=None,debug=0,errorlevel=1,stream=False)¶
All following arguments are optional and can be accessed as instance attributesas well.
name is the pathname of the archive.name may be apath-like object.It can be omitted iffileobj is given.In this case, the file object's
name
attribute is used if it exists.mode is either
'r'
to read from an existing archive,'a'
to appenddata to an existing file,'w'
to create a new file overwriting an existingone, or'x'
to create a new file only if it does not already exist.Iffileobj is given, it is used for reading or writing data. If it can bedetermined,mode is overridden byfileobj's mode.fileobj will be usedfrom position 0.
備註
fileobj is not closed, when
TarFile
is closed.format controls the archive format for writing. It must be one of the constants
USTAR_FORMAT
,GNU_FORMAT
orPAX_FORMAT
that aredefined at module level. When reading, format will be automatically detected, evenif different formats are present in a single archive.Thetarinfo argument can be used to replace the default
TarInfo
classwith a different one.Ifdereference is
False
, add symbolic and hard links to the archive. If itisTrue
, add the content of the target files to the archive. This has noeffect on systems that do not support symbolic links.Ifignore_zeros is
False
, treat an empty block as the end of the archive.If it isTrue
, skip empty (and invalid) blocks and try to get as many membersas possible. This is only useful for reading concatenated or damaged archives.debug can be set from
0
(no debug messages) up to3
(all debugmessages). The messages are written tosys.stderr
.errorlevel controls how extraction errors are handled,see
thecorrespondingattribute
.Theencoding anderrors arguments define the character encoding to beused for reading or writing the archive and how conversion errors are goingto be handled. The default settings will work for most users.See sectionUnicode issues for in-depth information.
Thepax_headers argument is an optional dictionary of strings whichwill be added as a pax global header ifformat is
PAX_FORMAT
.Ifstream is set to
True
then while reading the archive info about filesin the archive are not cached, saving memory.在 3.2 版的變更:Use
'surrogateescape'
as the default for theerrors argument.在 3.5 版的變更:The
'x'
(exclusive creation) mode was added.在 3.6 版的變更:Thename parameter accepts apath-like object.
在 3.13 版的變更:新增stream 參數。
- classmethodTarFile.open(...)¶
Alternative constructor. The
tarfile.open()
function is actually ashortcut to this classmethod.
- TarFile.getmember(name)¶
Return a
TarInfo
object for membername. Ifname can not be foundin the archive,KeyError
is raised.備註
If a member occurs more than once in the archive, its last occurrence is assumedto be the most up-to-date version.
- TarFile.getmembers()¶
Return the members of the archive as a list of
TarInfo
objects. Thelist has the same order as the members in the archive.
- TarFile.getnames()¶
Return the members as a list of their names. It has the same order as the listreturned by
getmembers()
.
- TarFile.list(verbose=True,*,members=None)¶
Print a table of contents to
sys.stdout
. Ifverbose isFalse
,only the names of the members are printed. If it isTrue
, outputsimilar to that ofls -l is produced. If optionalmembers isgiven, it must be a subset of the list returned bygetmembers()
.在 3.5 版的變更:新增members 參數。
- TarFile.next()¶
Return the next member of the archive as a
TarInfo
object, whenTarFile
is opened for reading. ReturnNone
if there is no moreavailable.
- TarFile.extractall(path='.',members=None,*,numeric_owner=False,filter=None)¶
Extract all members from the archive to the current working directory ordirectorypath. If optionalmembers is given, it must be a subset of thelist returned by
getmembers()
. Directory information like owner,modification time and permissions are set after all members have been extracted.This is done to work around two problems: A directory's modification time isreset each time a file is created in it. And, if a directory's permissions donot allow writing, extracting files to it will fail.Ifnumeric_owner is
True
, the uid and gid numbers from the tarfileare used to set the owner/group for the extracted files. Otherwise, the namedvalues from the tarfile are used.Thefilter argument specifies how
members
are modified or rejectedbefore extraction.SeeExtraction filters for details.It is recommended to set this explicitly depending on whichtar featuresyou need to support.警告
Never extract archives from untrusted sources without prior inspection.It is possible that files are created outside ofpath, e.g. membersthat have absolute filenames starting with
"/"
or filenames with twodots".."
.Set
filter='data'
to prevent the most dangerous security issues,and read theExtraction filters section for details.在 3.5 版的變更:新增numeric_owner 參數。
在 3.6 版的變更:Thepath parameter accepts apath-like object.
在 3.12 版的變更:新增filter 參數。
- TarFile.extract(member,path='',set_attrs=True,*,numeric_owner=False,filter=None)¶
Extract a member from the archive to the current working directory, using itsfull name. Its file information is extracted as accurately as possible.membermay be a filename or a
TarInfo
object. You can specify a differentdirectory usingpath.path may be apath-like object.File attributes (owner, mtime, mode) are set unlessset_attrs is false.Thenumeric_owner andfilter arguments are the same asfor
extractall()
.備註
The
extract()
method does not take care of several extraction issues.In most cases you should consider using theextractall()
method.警告
參閱
extractall()
的警告。Set
filter='data'
to prevent the most dangerous security issues,and read theExtraction filters section for details.在 3.2 版的變更:增加set_attrs 參數。
在 3.5 版的變更:新增numeric_owner 參數。
在 3.6 版的變更:Thepath parameter accepts apath-like object.
在 3.12 版的變更:新增filter 參數。
- TarFile.extractfile(member)¶
Extract a member from the archive as a file object.member may bea filename or a
TarInfo
object. Ifmember is a regular file ora link, anio.BufferedReader
object is returned. For all otherexisting members,None
is returned. Ifmember does not appearin the archive,KeyError
is raised.在 3.3 版的變更:Return an
io.BufferedReader
object.在 3.13 版的變更:The returned
io.BufferedReader
object has themode
attribute which is always equal to'rb'
.
- TarFile.errorlevel:int¶
Iferrorlevel is
0
, errors are ignored when usingTarFile.extract()
andTarFile.extractall()
.Nevertheless, they appear as error messages in the debug output whendebug is greater than 0.If1
(the default), allfatal errors are raised asOSError
orFilterError
exceptions. If2
, allnon-fatal errors are raisedasTarError
exceptions as well.Some exceptions, e.g. ones caused by wrong argument types or datacorruption, are always raised.
Customextraction filtersshould raise
FilterError
forfatal errorsandExtractError
fornon-fatal ones.Note that when an exception is raised, the archive may be partiallyextracted. It is the user’s responsibility to clean up.
- TarFile.extraction_filter¶
在 3.12 版被加入.
Theextraction filter usedas a default for thefilter argument of
extract()
andextractall()
.The attribute may be
None
or a callable.String names are not allowed for this attribute, unlike thefilterargument toextract()
.If
extraction_filter
isNone
(the default),calling an extraction method without afilter argument will raise aDeprecationWarning
,and fall back to thefully_trusted
filter,whose dangerous behavior matches previous versions of Python.In Python 3.14+, leaving
extraction_filter=None
will causeextraction methods to use thedata
filter by default.The attribute may be set on instances or overridden in subclasses.It also is possible to set it on the
TarFile
class itself to set aglobal default, although, since it affects all uses oftarfile,it is best practice to only do so in top-level applications orsiteconfiguration
.To set a global default this way, a filter function needs to be wrapped instaticmethod()
to prevent injection of aself
argument.
- TarFile.add(name,arcname=None,recursive=True,*,filter=None)¶
Add the filename to the archive.name may be any type of file(directory, fifo, symbolic link, etc.). If given,arcname specifies analternative name for the file in the archive. Directories are addedrecursively by default. This can be avoided by settingrecursive to
False
. Recursion adds entries in sorted order.Iffilter is given, itshould be a function that takes aTarInfo
object argument andreturns the changedTarInfo
object. If it instead returnsNone
theTarInfo
object will be excluded from thearchive. See範例 for an example.在 3.2 版的變更:新增filter 參數。
在 3.7 版的變更:Recursion adds entries in sorted order.
- TarFile.addfile(tarinfo,fileobj=None)¶
Add the
TarInfo
objecttarinfo to the archive. Iftarinfo representsa non zero-size regular file, thefileobj argument should be abinary file,andtarinfo.size
bytes are read from it and added to the archive. You cancreateTarInfo
objects directly, or by usinggettarinfo()
.在 3.13 版的變更:fileobj must be given for non-zero-sized regular files.
- TarFile.gettarinfo(name=None,arcname=None,fileobj=None)¶
Create a
TarInfo
object from the result ofos.stat()
orequivalent on an existing file. The file is either named byname, orspecified as afile objectfileobj with a file descriptor.name may be apath-like object. Ifgiven,arcname specifies an alternative name for the file in thearchive, otherwise, the name is taken fromfileobj’sname
attribute, or thename argument. The nameshould be a text string.You can modifysome of the
TarInfo
’s attributes before you add it usingaddfile()
.If the file object is not an ordinary file object positioned at thebeginning of the file, attributes such assize
may needmodifying. This is the case for objects such asGzipFile
.Thename
may also be modified, in which casearcnamecould be a dummy string.在 3.6 版的變更:Thename parameter accepts apath-like object.
TarInfo 物件¶
ATarInfo
object represents one member in aTarFile
. Asidefrom storing all required attributes of a file (like file type, size, time,permissions, owner etc.), it provides some useful methods to determine its type.It doesnot contain the file's data itself.
TarInfo
objects are returned byTarFile
's methodsgetmember()
,getmembers()
andgettarinfo()
.
Modifying the objects returned bygetmember()
orgetmembers()
will affect all subsequentoperations on the archive.For cases where this is unwanted, you can usecopy.copy()
orcall thereplace()
method to create a modified copy in one step.
Several attributes can be set toNone
to indicate that a piece of metadatais unused or unknown.DifferentTarInfo
methods handleNone
differently:
The
extract()
orextractall()
methods willignore the corresponding metadata, leaving it set to a default.addfile()
will fail.list()
will print a placeholder string.
- classmethodTarInfo.frombuf(buf,encoding,errors)¶
Create and return a
TarInfo
object from string bufferbuf.Raises
HeaderError
if the buffer is invalid.
- classmethodTarInfo.fromtarfile(tarfile)¶
Read the next member from the
TarFile
objecttarfile and return it asaTarInfo
object.
- TarInfo.tobuf(format=DEFAULT_FORMAT,encoding=ENCODING,errors='surrogateescape')¶
Create a string buffer from a
TarInfo
object. For information on thearguments see the constructor of theTarFile
class.在 3.2 版的變更:Use
'surrogateescape'
as the default for theerrors argument.
ATarInfo
object has the following public data attributes:
- TarInfo.mtime:int|float¶
Time of last modification in seconds since theepoch,as in
os.stat_result.st_mtime
.在 3.12 版的變更:Can be set to
None
forextract()
andextractall()
, causing extraction to skip applying thisattribute.
- TarInfo.mode:int¶
Permission bits, as for
os.chmod()
.在 3.12 版的變更:Can be set to
None
forextract()
andextractall()
, causing extraction to skip applying thisattribute.
- TarInfo.type¶
File type.type is usually one of these constants:
REGTYPE
,AREGTYPE
,LNKTYPE
,SYMTYPE
,DIRTYPE
,FIFOTYPE
,CONTTYPE
,CHRTYPE
,BLKTYPE
,GNUTYPE_SPARSE
. To determine the type of aTarInfo
objectmore conveniently, use theis*()
methods below.
- TarInfo.linkname:str¶
Name of the target file name, which is only present in
TarInfo
objectsof typeLNKTYPE
andSYMTYPE
.For symbolic links (
SYMTYPE
), thelinkname is relative to the directorythat contains the link.For hard links (LNKTYPE
), thelinkname is relative to the root ofthe archive.
- TarInfo.uid:int¶
User ID of the user who originally stored this member.
在 3.12 版的變更:Can be set to
None
forextract()
andextractall()
, causing extraction to skip applying thisattribute.
- TarInfo.gid:int¶
Group ID of the user who originally stored this member.
在 3.12 版的變更:Can be set to
None
forextract()
andextractall()
, causing extraction to skip applying thisattribute.
- TarInfo.uname:str¶
User name.
在 3.12 版的變更:Can be set to
None
forextract()
andextractall()
, causing extraction to skip applying thisattribute.
- TarInfo.gname:str¶
Group name.
在 3.12 版的變更:Can be set to
None
forextract()
andextractall()
, causing extraction to skip applying thisattribute.
- TarInfo.sparse¶
Sparse member information.
- TarInfo.pax_headers:dict¶
A dictionary containing key-value pairs of an associated pax extended header.
- TarInfo.replace(name=...,mtime=...,mode=...,linkname=...,uid=...,gid=...,uname=...,gname=...,deep=True)¶
在 3.12 版被加入.
Return anew copy of the
TarInfo
object with the given attributeschanged. For example, to return aTarInfo
with the group name set to'staff'
, use:new_tarinfo=old_tarinfo.replace(gname='staff')
By default, a deep copy is made.Ifdeep is false, the copy is shallow, i.e.
pax_headers
and any custom attributes are shared with the originalTarInfo
object.
ATarInfo
object also provides some convenient query methods:
Extraction filters¶
在 3.12 版被加入.
Thetar format is designed to capture all details of a UNIX-like filesystem,which makes it very powerful.Unfortunately, the features make it easy to create tar files that haveunintended -- and possibly malicious -- effects when extracted.For example, extracting a tar file can overwrite arbitrary files in variousways (e.g. by using absolute paths,..
path components, or symlinks thataffect later members).
In most cases, the full functionality is not needed.Therefore,tarfile supports extraction filters: a mechanism to limitfunctionality, and thus mitigate some of the security issues.
也參考
- PEP 706
Contains further motivation and rationale behind the design.
Thefilter argument toTarFile.extract()
orextractall()
can be:
the string
'fully_trusted'
: Honor all metadata as specified in thearchive.Should be used if the user trusts the archive completely, or implementstheir own complex verification.the string
'tar'
: Honor mosttar-specific features (i.e. features ofUNIX-like filesystems), but block features that are very likely to besurprising or malicious. Seetar_filter()
for details.the string
'data'
: Ignore or block most features specific to UNIX-likefilesystems. Intended for extracting cross-platform data archives.Seedata_filter()
for details.None
(default): UseTarFile.extraction_filter
.If that is also
None
(the default), raise aDeprecationWarning
,and fall back to the'fully_trusted'
filter, whose dangerous behaviormatches previous versions of Python.In Python 3.14, the
'data'
filter will become the default instead.It's possible to switch earlier; seeTarFile.extraction_filter
.A callable which will be called for each extracted member with aTarInfo describing the member and the destinationpath to where the archive is extracted (i.e. the same path is used for allmembers):
filter(member:TarInfo,path:str,/)->TarInfo|None
The callable is called just before each member is extracted, so it cantake the current state of the disk into account.It can:
return a
TarInfo
object which will be used instead of the metadatain the archive, orreturn
None
, in which case the member will be skipped, orraise an exception to abort the operation or skip the member,depending on
errorlevel
.Note that when extraction is aborted,extractall()
may leavethe archive partially extracted. It does not attempt to clean up.
Default named filters¶
The pre-defined, named filters are available as functions, so they can bereused in custom filters:
- tarfile.fully_trusted_filter(member,path)¶
Returnmember unchanged.
This implements the
'fully_trusted'
filter.
- tarfile.tar_filter(member,path)¶
Implements the
'tar'
filter.Strip leading slashes (
/
andos.sep
) from filenames.Refuse to extract files with absolutepaths (in case the name is absoluteeven after stripping slashes, e.g.
C:/foo
on Windows).This raisesAbsolutePathError
.Refuse to extract files whose absolutepath (after following symlinks) would end up outside the destination.This raises
OutsideDestinationError
.Clear high mode bits (setuid, setgid, sticky) and group/other write bits(
S_IWGRP
|S_IWOTH
).
Return the modified
TarInfo
member.
- tarfile.data_filter(member,path)¶
Implements the
'data'
filter.In addition to whattar_filter
does:Refuse to extract links (hard or soft)that link to absolute paths, or ones that link outside the destination.
This raises
AbsoluteLinkError
orLinkOutsideDestinationError
.Note that such files are refused even on platforms that do not supportsymbolic links.
Refuse to extract device files(including pipes).This raises
SpecialFileError
.For regular files, including hard links:
For other files (directories), set
mode
toNone
, sothat extraction methods skip applying permission bits.Set user and group info (
uid
,gid
,uname
,gname
)toNone
, so that extraction methods skip setting it.
Return the modified
TarInfo
member.
Filter errors¶
When a filter refuses to extract a file, it will raise an appropriate exception,a subclass ofFilterError
.This will abort the extraction ifTarFile.errorlevel
is 1 or more.Witherrorlevel=0
the error will be logged and the member will be skipped,but extraction will continue.
Hints for further verification¶
Even withfilter='data'
,tarfile is not suited for extracting untrustedfiles without prior inspection.Among other issues, the pre-defined filters do not prevent denial-of-serviceattacks. Users should do additional checks.
Here is an incomplete list of things to consider:
Extract to a
newtemporarydirectory
to prevent e.g. exploiting pre-existing links, and to make it easier toclean up after a failed extraction.When working with untrusted data, use external (e.g. OS-level) limits ondisk, memory and CPU usage.
Check filenames against an allow-list of characters(to filter out control characters, confusables, foreign path separators,etc.).
Check that filenames have expected extensions (discouraging files thatexecute when you “click on them”, or extension-less files like Windows special device names).
Limit the number of extracted files, total size of extracted data,filename length (including symlink length), and size of individual files.
Check for files that would be shadowed on case-insensitive filesystems.
Also note that:
Tar files may contain multiple versions of the same file.Later ones are expected to overwrite any earlier ones.This feature is crucial to allow updating tape archives, but can be abusedmaliciously.
tarfile does not protect against issues with “live” data,e.g. an attacker tinkering with the destination (or source) directory whileextraction (or archiving) is in progress.
Supporting older Python versions¶
Extraction filters were added to Python 3.12, but may be backported to olderversions as security updates.To check whether the feature is available, use e.g.hasattr(tarfile,'data_filter')
rather than checking the Python version.
The following examples show how to support Python versions with and withoutthe feature.Note that settingextraction_filter
will affect any subsequent operations.
Fully trusted archive:
my_tarfile.extraction_filter=(lambdamember,path:member)my_tarfile.extractall()
Use the
'data'
filter if available, but revert to Python 3.11 behavior('fully_trusted'
) if this feature is not available:my_tarfile.extraction_filter=getattr(tarfile,'data_filter',(lambdamember,path:member))my_tarfile.extractall()
Use the
'data'
filter;fail if it is not available:my_tarfile.extractall(filter=tarfile.data_filter)
或:
my_tarfile.extraction_filter=tarfile.data_filtermy_tarfile.extractall()
Use the
'data'
filter;warn if it is not available:ifhasattr(tarfile,'data_filter'):my_tarfile.extractall(filter='data')else:# remove this when no longer neededwarn_the_user('Extracting may be unsafe; consider updating Python')my_tarfile.extractall()
Stateful extraction filter example¶
Whiletarfile's extraction methods take a simplefilter callable,custom filters may be more complex objects with an internal state.It may be useful to write these as context managers, to be used like this:
withStatefulFilter()asfilter_func:tar.extractall(path,filter=filter_func)
Such a filter can be written as, for example:
classStatefulFilter:def__init__(self):self.file_count=0def__enter__(self):returnselfdef__call__(self,member,path):self.file_count+=1returnmemberdef__exit__(self,*exc_info):print(f'{self.file_count} files extracted')
Command-Line Interface¶
在 3.4 版被加入.
Thetarfile
module provides a simple command-line interface to interactwith tar archives.
If you want to create a new tar archive, specify its name after the-c
option and then list the filename(s) that should be included:
$python-mtarfile-cmonty.tarspam.txteggs.txt
Passing a directory is also acceptable:
$python-mtarfile-cmonty.tarlife-of-brian_1979/
If you want to extract a tar archive into the current directory, usethe-e
option:
$python-mtarfile-emonty.tar
You can also extract a tar archive into a different directory by passing thedirectory's name:
$python-mtarfile-emonty.tarother-dir/
For a list of the files in a tar archive, use the-l
option:
$python-mtarfile-lmonty.tar
命令列選項¶
- -c<tarfile><source1>...<sourceN>¶
- --create<tarfile><source1>...<sourceN>¶
Create tarfile from source files.
- -e<tarfile>[<output_dir>]¶
- --extract<tarfile>[<output_dir>]¶
Extract tarfile into the current directory ifoutput_dir is not specified.
- -v,--verbose¶
Verbose output.
- --filter<filtername>¶
Specifies thefilter for
--extract
.SeeExtraction filters for details.Only string names are accepted (that is,fully_trusted
,tar
,anddata
).
範例¶
How to extract an entire tar archive to the current working directory:
importtarfiletar=tarfile.open("sample.tar.gz")tar.extractall(filter='data')tar.close()
How to extract a subset of a tar archive withTarFile.extractall()
usinga generator function instead of a list:
importosimporttarfiledefpy_files(members):fortarinfoinmembers:ifos.path.splitext(tarinfo.name)[1]==".py":yieldtarinfotar=tarfile.open("sample.tar.gz")tar.extractall(members=py_files(tar))tar.close()
How to create an uncompressed tar archive from a list of filenames:
importtarfiletar=tarfile.open("sample.tar","w")fornamein["foo","bar","quux"]:tar.add(name)tar.close()
The same example using thewith
statement:
importtarfilewithtarfile.open("sample.tar","w")astar:fornamein["foo","bar","quux"]:tar.add(name)
How to read a gzip compressed tar archive and display some member information:
importtarfiletar=tarfile.open("sample.tar.gz","r:gz")fortarinfointar:print(tarinfo.name,"is",tarinfo.size,"bytes in size and is ",end="")iftarinfo.isreg():print("a regular file.")eliftarinfo.isdir():print("a directory.")else:print("something else.")tar.close()
How to create an archive and reset the user information using thefilterparameter inTarFile.add()
:
importtarfiledefreset(tarinfo):tarinfo.uid=tarinfo.gid=0tarinfo.uname=tarinfo.gname="root"returntarinfotar=tarfile.open("sample.tar.gz","w:gz")tar.add("foo",filter=reset)tar.close()
Supported tar formats¶
There are three tar formats that can be created with thetarfile
module:
The POSIX.1-1988 ustar format (
USTAR_FORMAT
). It supports filenamesup to a length of at best 256 characters and linknames up to 100 characters.The maximum file size is 8 GiB. This is an old and limited but widelysupported format.The GNU tar format (
GNU_FORMAT
). It supports long filenames andlinknames, files bigger than 8 GiB and sparse files. It is the de factostandard on GNU/Linux systems.tarfile
fully supports the GNU tarextensions for long names, sparse file support is read-only.The POSIX.1-2001 pax format (
PAX_FORMAT
). It is the most flexibleformat with virtually no limits. It supports long filenames and linknames, largefiles and stores pathnames in a portable way. Modern tar implementations,including GNU tar, bsdtar/libarchive and star, fully support extendedpaxfeatures; some old or unmaintained libraries may not, but should treatpax archives as if they were in the universally supportedustar format.It is the current default format for new archives.It extends the existingustar format with extra headers for informationthat cannot be stored otherwise. There are two flavours of pax headers:Extended headers only affect the subsequent file header, globalheaders are valid for the complete archive and affect all following files.All the data in a pax header is encoded inUTF-8 for portability reasons.
There are some more variants of the tar format which can be read, but notcreated:
The ancient V7 format. This is the first tar format from Unix Seventh Edition,storing only regular files and directories. Names must not be longer than 100characters, there is no user/group name information. Some archives havemiscalculated header checksums in case of fields with non-ASCII characters.
The SunOS tar extended format. This format is a variant of the POSIX.1-2001pax format, but is not compatible.
Unicode issues¶
The tar format was originally conceived to make backups on tape drives with themain focus on preserving file system information. Nowadays tar archives arecommonly used for file distribution and exchanging archives over networks. Oneproblem of the original format (which is the basis of all other formats) isthat there is no concept of supporting different character encodings. Forexample, an ordinary tar archive created on aUTF-8 system cannot be readcorrectly on aLatin-1 system if it contains non-ASCII characters. Textualmetadata (like filenames, linknames, user/group names) will appear damaged.Unfortunately, there is no way to autodetect the encoding of an archive. Thepax format was designed to solve this problem. It stores non-ASCII metadatausing the universal character encodingUTF-8.
The details of character conversion intarfile
are controlled by theencoding anderrors keyword arguments of theTarFile
class.
encoding defines the character encoding to use for the metadata in thearchive. The default value issys.getfilesystemencoding()
or'ascii'
as a fallback. Depending on whether the archive is read or written, themetadata must be either decoded or encoded. Ifencoding is not setappropriately, this conversion may fail.
Theerrors argument defines how characters are treated that cannot beconverted. Possible values are listed in sectionError Handlers.The default scheme is'surrogateescape'
which Python also uses for itsfile system calls, seeFile Names, Command Line Arguments, and Environment Variables.
ForPAX_FORMAT
archives (the default),encoding is generally not neededbecause all the metadata is stored usingUTF-8.encoding is only used inthe rare cases when binary pax headers are decoded or when strings withsurrogate characters are stored.