Re: priviledge seperation not working like before

What's the deal with configure these days (say it like Jerry Seinfeld)?

You won't see anything pointing to /var/empty because that is the processes chrooted directory. /var/empty isn't actually open until you try to list files in there. An easy way to confirm this would be to remove /var/empty. If you can't login, chances are, it's working. I'm sure the list will provide a better method, but that's a dirty way to check.

-James

list1@0ff.org wrote:

> In English that means what? I did an lsof on all the pids ..saw nothing 
> pointing to /var/empty...its working? It would be especially helpful to 
> have a way to confirm it. And what's the deal with the ./configure not 
> failing if you specify a non existent user as the privsep-user? Ideas?
> 
> thanks again,
> 
> Cherie
> 
> 
> At 02:31 PM 2/13/2003 -0600, you wrote:
> 
> 

> 
> 
> 
> 

-- 
James Dennis
Harvard Law School

"Not everything that counts can be counted,
and not everything that can be counted counts."