From owner-freebsd-bugs@FreeBSD.ORG  Sat Jun 26 08:00:59 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7B4E116A4CE; Sat, 26 Jun 2004 08:00:59 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 61AE243D4C; Sat, 26 Jun 2004 08:00:59 +0000 (GMT)
	(envelope-from csjp@FreeBSD.org)
Received: from freefall.freebsd.org (csjp@localhost [127.0.0.1])
	i5Q804ri005935;	Sat, 26 Jun 2004 08:00:04 GMT
	(envelope-from csjp@freefall.freebsd.org)
Received: (from csjp@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5Q803Uw005931;
	Sat, 26 Jun 2004 08:00:03 GMT
	(envelope-from csjp)
Date: Sat, 26 Jun 2004 08:00:03 GMT
From: "Christian S.J. Peron" <csjp@FreeBSD.org>
Message-Id: <200406260800.i5Q803Uw005931@freefall.freebsd.org>
To: csjp@FreeBSD.org, freebsd-bugs@FreeBSD.org, csjp@FreeBSD.org
Subject: Re: bin/68165: df fails to check fs type with -t and inaccessible
	mount point
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Jun 2004 08:00:59 -0000

Synopsis: df fails to check fs type with -t and inaccessible mount point

Responsible-Changed-From-To: freebsd-bugs->csjp
Responsible-Changed-By: csjp
Responsible-Changed-When: Sat Jun 26 07:56:05 GMT 2004
Responsible-Changed-Why: 
I will take this one.  This PR brings up a more interesting
problem, if the parent directory of a mount point does not
have execute-search permissions, should the user be able
to access any information about the mount point in the
first place, as the path to the mount-point itself exposes
a filename within a restricted directory.

http://www.freebsd.org/cgi/query-pr.cgi?pr=68165