Subject: re: bin/30132: Something is wrong with tar(1) --chroot
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org>
From: matthew green <mrg@eterna.com.au>
List: netbsd-bugs
Date: 05/05/2005 13:08:02
The following reply was made to PR bin/30132; it has been noted by GNATS.
From: matthew green <mrg@eterna.com.au>
To: christos@zoulas.com (Christos Zoulas)
Cc: gnats-bugs@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: re: bin/30132: Something is wrong with tar(1) --chroot
Date: Thu, 05 May 2005 23:07:17 +1000
| i don't think this is the correct answer. the tarballs that are failing
| to extract are netbsd sets. afaik, those all have files that start with
| "./" in them. to me this implies that whatever tests you have added for
| checking extraction has not changed location are broken in the precense
presence, of course :-)
| of the --chroot flag.
|
| surely you aren't suggesting that sysinst needs to pass --insecure?
I thought that they start with / not ./ reading from the output of tar.
Are you sure that they start with ./?
pretty sure. otherwise extracting them into a NFS client root dir
would be dangerous. and, sure enough, the sparc world i built a
few days ago tells me:
splode sparc/binary/sets> foreach a ( *.tgz )
foreach? pax -z < $a | grep -v '^\./|^\.$'
foreach? end
splode sparc/binary/sets>
ie, no files that are not "." or don't start with "./".