X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;ds=sidebyside;f=doc%2Ftar.texi;h=6a91f7642dd995ff731e6b9d14e7aec79d0ea879;hb=33b04d5ecddd98d61d07b1d9000e1fffa6e00a16;hp=5a1f9204384ce295f9413833283b42fc6e628493;hpb=317fbb9d5f33d8dff837ac6354b917940aa2e8d8;p=chaz%2Ftar

diff --git a/doc/tar.texi b/doc/tar.texi
index 5a1f920..6a91f76 100644
--- a/doc/tar.texi
+++ b/doc/tar.texi
@@ -1802,6 +1802,7 @@ long form of the operation without affecting the performance.
 * extracting archives::
 * extracting files::
 * extract dir::
+* extracting untrusted archives::
 * failing commands::
 @end menu
 
@@ -1922,6 +1923,23 @@ of the file names when you extract those files from the archive.
 @FIXME{IMPORTANT!  show the final structure, here.  figure out what it
 will be.}
 
+@node extracting untrusted archives
+@subsection Extracting Archives from Untrusted Sources
+
+Extracting files from archives can overwrite files that already exist.
+If you receive an archive from an untrusted source, you should make a
+new directory and extract into that directory, so that you don't have
+to worry about the extraction overwriting one of your existing files.
+For example, if @file{untrusted.tar} came from somewhere else on the
+Internet, and you don't necessarily trust its contents, you can
+extract it as follows:
+
+@example
+$ @kbd{mkdir newdir}
+$ @kbd{cd newdir}
+$ @kbd{tar -xvf ../untrusted.tar}
+@end example
+
 @node failing commands
 @subsection Commands That Will Fail