From owner-freebsd-hackers Mon Apr 2 1: 0:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4FF8337B71C; Mon, 2 Apr 2001 01:00:25 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f3280Nq11333; Mon, 2 Apr 2001 02:00:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200104020800.f3280Nq11333@harmony.village.org> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Security problems with access(2)? Cc: Greg Black , Robert Watson , Bill Moran In-reply-to: Your message of "Sun, 01 Apr 2001 19:04:58 PDT." <20010401190458.A4991@dragon.nuxi.com> References: <20010401190458.A4991@dragon.nuxi.com> Date: Mon, 02 Apr 2001 01:59:07 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010401190458.A4991@dragon.nuxi.com> "David O'Brien" writes: : On Sun, Apr 01, 2001 at 10:55:23AM +1000, Greg Black wrote: : > Many years ago I implemented a new interface that I called : > eaccess() which replicated the work of access, but tested : > against the effective uid and gid. I'd like to see that : > introduced more widely. : : That still isn't suffient (and even more scary) unless the parameter is a : file handle or FILE pointer. We need an faccess() call, plain and : simple. faccess is also dangarous. When you open the file at elevated privs, you run the risk of side effects, such as a tape rewinding on close. facecss won't change that problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message