Re: Why are exe, cwd, and root priviledged bits of information?

[jw schultz]

On Thu, Nov 07, 2002 at 11:05:21AM -0500, Daniel Jacobowitz wrote:
> On Thu, Nov 07, 2002 at 10:57:06AM -0500, Calin A. Culianu wrote:
> > 
> > In the /prod/PID subset of procfs, why are the exe, cwd, and root symlinks
> > considered priviledged information?
> > 
> > Exe is the big one for me, as this one can be usually infered from reading
> > /prod/PID/maps.  Root I guess can't be inferred in any unpriviledged way,
> > and neither can cwd.  At any rate.. I am not sure behind the philosophy to
> > make these symlinks' destinations priviledged...  can someone clarify
> > this?
> 
> This came up a little while ago.  The answer is that maps should be
> priviledged also.
> 
> For instance:
>   You can protect a directory by giving its parent directory no read
> permissions.  The name of the directory is now secret.  You don't want
> to reveal it in cwd.
> 

Daniel is correct in that the issue came up recently.  He
gives _his_ answer above.  If you believe in security
through obscurity you will agree with him.  I don't.
I will agree that there should be no real reason to need
access to this information.

With ACLs you will be able to explicitly grant access and
you won't have to depend on keeping shared info secret.
Then this will be less of an issue.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		[e-mail]

		Remember Cernan and Schmitt