Date: Mon, 10 May 2004 18:40:08 +0200 From: Marc Olzheim <marcolz@stack.nl> To: Tim Robbins <tjr@freebsd.org> Cc: freebsd-current@www.freebsd.org Subject: Re: Unified getcwd() implementation Message-ID: <20040510164008.GA5960@stack.nl> In-Reply-To: <20040508151412.GA21857@cat.robbins.dropbear.id.au> References: <20040507092235.GA61837@stack.nl> <20040507100119.GA15782@cat.robbins.dropbear.id.au> <20040507235556.GB37035@empiric.dek.spc.org> <20040508010228.GA18935@cat.robbins.dropbear.id.au> <20040508012357.GA37547@empiric.dek.spc.org> <20040508030258.GA19512@cat.robbins.dropbear.id.au> <20040508044207.GB38736@empiric.dek.spc.org> <20040508070040.GA20138@cat.robbins.dropbear.id.au> <20040508135954.GA469@stack.nl> <20040508151412.GA21857@cat.robbins.dropbear.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 09, 2004 at 01:14:12AM +1000, Tim Robbins wrote: > > - getcwd() having elevated permission to actually be able to find the > > real cwd. > > >From what I can see, it still uses the caller's credentials in calls > to VOP_GETATTR(), VOP_LOOKUP() and VOP_READDIR(). Erhm yes, you're right. That will be in the next patch. Perhaps yet another sysctl to allow for per machine setting of allowing getcwd() to resolv unreadable paths ? That would be necessary for the linuxulator anyhow... Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040510164008.GA5960>