From b0e8ba8839adae0872274d74739d60dd88cf16e6 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Mon, 22 Sep 2003 18:26:50 +0000 Subject: [PATCH] (extracting untrusted archives): New section. --- doc/tar.texi | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) 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 -- 2.45.2