From owner-freebsd-bugs@FreeBSD.ORG Sun Apr 10 14:40:12 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 467EE106564A for ; Sun, 10 Apr 2011 14:40:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 341EA8FC17 for ; Sun, 10 Apr 2011 14:40:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3AEeCqB072033 for ; Sun, 10 Apr 2011 14:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3AEeCO9072032; Sun, 10 Apr 2011 14:40:12 GMT (envelope-from gnats) Date: Sun, 10 Apr 2011 14:40:12 GMT Message-Id: <201104101440.p3AEeCO9072032@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Mikolaj Golub Cc: Subject: Re: misc/156225: test -x under root in bash shell returns incorrect results X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mikolaj Golub List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2011 14:40:12 -0000 The following reply was made to PR misc/156225; it has been noted by GNATS. From: Mikolaj Golub To: remko@FreeBSD.org, cmyk777@gmail.com, bug-followup@FreeBSD.org Cc: Subject: Re: misc/156225: test -x under root in bash shell returns incorrect results Date: Sun, 10 Apr 2011 17:33:29 +0300 Bash checks permission calling eaccess(2). The issue is that it returns success for root: 19632 bash CALL eaccess(0x28417600,X_OK) 19632 bash NAMI "/root/.cshrc" 19632 bash RET eaccess 0 sh's test has a workaround for this: case FILEX: /* XXX work around eaccess(2) false positives for superuser */ if (eaccess(nm, X_OK) != 0) return 0; if (S_ISDIR(s.st_mode) || geteuid() != 0) return 1; The eaccess(2) behaviour has been changed in CURRENT. See kern/125009 for details. I think this ticket can be set as a duplicate of kern/125009. -- Mikolaj Golub