Unpatched versions of Python

Tools are allowed to ignore this PEP when running on Python without tarfilefilters.

The feature has been backported to all versions of Python supported bypython.org. Vendoring it in third-party libraries is tricky,and we should not force all tools to do so.This shifts the responsibility to keep up with security updates from the toolsto the users.

Permissions

Common tools (git,zip) don’t preserve Unix permissions (mode bits).Telling users to not rely on them insdists, and allowing tools to handlethem relatively freely, seems fair.

The only exception is theexecutable permission.We recommend, but not require, that tools preserve it.Given that scripts are generally platform-specific, it seems fitting tosay that keeping them executable is tool-specific behaviour.

Note that whilegit preserves executability,zip (and thuswheel)doesn’t do it natively. (It is possible to encode it in “external attributes”,but Python’sZipFile.extract does not honour that.)

Unpacking with the data filter

When extracting a source distribution, tools MUST either usetarfile.data_filter (e.g.TarFile.extractall(...,filter='data')), ORfollow theUnpacking without the data filter section below.

As an exception, on Python interpreters withouthasattr(tarfile,'data_filter')(PEP 706), tools that normally use that filter (directly on indirectly)MAY warn the user and ignore this specification.The trade-off between usability (e.g. fully trusting the archive) andsecurity (e.g. refusing to unpack) is left up to the tool in this case.

Unpacking without the data filter

Tools that do not use thedata filter directly (e.g. for backwardscompatibility, allowing additional features, or not using Python) MUST followthis section.(At the time of this writing, thedata filter also follows this section,but it may get out of sync in the future.)

The following files are invalid in ansdist archive.Upon encountering such an entry, tools SHOULD notify the user,MUST NOT unpack the entry, and MAY abort with a failure:

• Files that would be placed outside the destination directory.
• Links (symbolic or hard) pointing outside the destination directory.
• Device files (including pipes).

The following are also invalid. Tools MAY treat them as above,but are NOT REQUIRED to do so:

• Files with a.. component in the filename or link target.
• Links pointing to a file that is not part of the archive.

Tools MAY unpack links (symbolic or hard) as regular files,using content from the archive.

When extractingsdist archives:

• Leading slashes in file names MUST be dropped.(This is nowadays standard behaviour fortar unpacking.)
• For eachmode (Unix permission) bit, tools MUST either:
  • use the platform’s default for a new file/directory (respectively),
  • set the bit according to the archive, or
  • use the bit fromrw-r--r-- (0o644) for non-executable files orrwxr-xr-x (0o755) for executable files and directories.
• Highmode bits (setuid, setgid, sticky) MUST be cleared.
• It is RECOMMENDED to preserve the userexecutable bit.

Further hints

Tool authors are encouraged to consider howhints for furtherverification intarfile documentation apply for their tool.