Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Tar (computing)
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Tarbomb=== {{redirect-distinguish|Tarbomb|zip bomb}} A '''tarbomb''', in [[Jargon File|hacker slang]], is a tarball containing a large number of items whose contents are written to the current directory or some other existing directory when untarred instead of the directory created by the tarball specifically for the extracted outputs. <ref>{{cite web |title=Tarbomb Definition |language=en |website=[[The Linux Info Project]] |url=https://www.linfo.org/tarbomb.html |access-date=2024-12-12 }}</ref> It is at best an inconvenience to the user, who is obliged to identify and delete a number of files interspersed with the directory's other contents. Such behavior is considered bad etiquette on the part of the archive's creator. A related problem is the use of [[Path (computing)|absolute path]]s or [[Directory (computing)|parent directory]] references when creating tar files. Files extracted from such archives will often be created in unusual locations outside the working directory and, like a tarbomb, have the potential to overwrite existing files. However, modern versions of FreeBSD and GNU tar do not create or extract absolute paths and parent-directory references by default, unless it is explicitly allowed with the flag {{code|-P}} or the option {{code|--absolute-names}}. The bsdtar program, which is also available on many operating systems and is the default tar implementation on [[macOS|Mac OS X]] v10.6, also does not follow parent-directory references or symbolic links.<ref>{{Cite web|url=https://man.freebsd.org/cgi/man.cgi?query=bsdtar&sektion=1&format=html|title=bsdtar(1)|website=man.freebsd.org}}</ref> <!-- https://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man1/bsdtar.1.html Man page for "bsdtar", as provided by Apple. -->{{failed verification|date=July 2022}} If a user has only a very old tar available, which does not feature those security measures, these problems can be mitigated by first examining a tar file using the command <code>tar tf archive.tar</code>, which lists the contents and allows to exclude problematic files afterwards. These commands do not extract any files, but display the names of all files in the archive. If any are problematic, the user can create a new empty directory and extract the archive into itβor avoid the tar file entirely. Most graphical tools can display the contents of the archive before extracting them. [[Vim (text editor)|Vim]] can open tar archives and display their contents. [[GNU Emacs]] is also able to open a tar archive and display its contents in a [[dired]] buffer.
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Tar (computing)
(section)
Add topic