Re: get git not to care about permissions

From: Thomas Rast <trast@student.ethz.ch>
Date: Nov 15, 2009, 12:31 UTC
Message-ID: <200911151331.35787.trast@student.ethz.ch>
In-Reply-To: <3cf217d80911121344w7d1809ebs103eaa2ac19a03a6@mail.gmail.com>

Matt Schoen wrote:

Show 14 quoted lines

> On Thu, Nov 12, 2009 at 11:10 AM, Thomas Rast <trast@student.ethz.ch> wrote:
> > It prints an absolute path, so the open() also accesses an absolute
> > path (though I don't know why it insists on that).
> >
> > But the above directory listing would indicate that you do not even
> > have permission to look inside your $(pwd) by absolute path...
> 
> I'm pretty sure I can.  How can I test this?  I can ls all
> subdirectories within the path, and when I navigate to the path, I
> usually do it absolutely.  After all, this is a network share, so I
> have to start with "/ad/eng/...".  Although, this is curious.  Some of
> the directories show "d---------" when I do ls -al.  They were created
> by root in the same environment (forced 700), but I can still read
> their contents, and such.

What filesystem is this? Are there perhaps extended attributes allowing access anyway? I'm not exactly an expert on unix permissions but my local path_resolution(7) tells me it should not be possible to cd beyond a directory where you have no 'x' permissions.

> Does open() strictly require the permissions you give it?

open(2) says the permissions are modified by the umask, so that shouldn't be a problem.

Question for the people who know git better than me: Does that open() require an absolute path?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch