From owner-freebsd-stable@FreeBSD.ORG Mon Oct 20 09:22:14 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C919550B for ; Mon, 20 Oct 2014 09:22:14 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8A368622 for ; Mon, 20 Oct 2014 09:22:14 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1Xg9AE-0008Kn-K1 for freebsd-stable@freebsd.org; Mon, 20 Oct 2014 11:22:11 +0200 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: 10.1-RC1 tar(1) spurious directory traversal permission error References: <20141020090424.GB1120@rwpc15.gfn.riverwillow.net.au> Date: Mon, 20 Oct 2014 11:22:05 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20141020090424.GB1120@rwpc15.gfn.riverwillow.net.au> User-Agent: Opera Mail/12.17 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, BAYES_20 autolearn=disabled version=3.3.1 X-Scan-Signature: 5a1627636b35b65657045ef62631cd80 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2014 09:22:14 -0000 On Mon, 20 Oct 2014 11:04:24 +0200, John Marshall wrote: > I don't know if tar(1) is the culprit or an innocent bystander but this > is what I am seeing on 10.1-RC1 (r272468 amd64). The archive appears to > be written properly prior to generation of the error message. Although > the user is permitted to traverse the parent directory, tar(1) emits the > complaint if the parent directory is not readable. Filesystem is UFS. > > $ tar -czf dtt.tgz -C /data/tftp/thlan . > tar: .: Unable to continue traversing directory tree: Permission denied > tar: Error exit delayed from previous errors. > $ > > $ ls -ld /data /data/tftp /data/tftp/thlan > drwxr-xr-x 33 root wheel 1024 2 Sep 20:13 /data > drwxr-x--x 4 root wheel 512 23 Apr 09:00 /data/tftp > drwxr-x--x 3 john wheel 512 23 Apr 10:28 /data/tftp/thlan > > # chmod o+r /data/tftp > > $ tar -czf dtt.tgz -C /data/tftp/thlan . > $ > > I haven't played with 10.0 but this behaviour is different to other > earlier releases (e.g. 9.3-RELEASE doesn't do this). > > I have filed a PR [Bug 194477]. > Maybe the output of 'truss -o /tmp/truss.txt tar -czf dtt.tgz -C /data/tftp/thlan .' gives interesting information about what is exactly giving the permission denied. Ronald.