Re: policy question

[Tom <tom@lemuria.org>]

On Thu, Apr 18, 2002 at 12:44:24PM +0200, Russell Coker wrote:
> > Scenario: Webhosting with PHP, multiple users (possibly many)
> > Danger: PHP runs as a module, i.e. with apache's user and permissions.
> 
> Here's the problem, not just for SE Linux but also for regular Unix 
> permissions models and every other security system I know of.

Absolutely. The problem is that you have a unified frontend with
diversification at the backend. This is the same issue you have for
ssh, except that ssh (and other remote login tools) have a method for
changing to a specific user, based on user/password data.


> Trying to give access to only code from a certain shared object inside a 
> program is never going to work.  Anything Apache can do to get access, some 
> malicious code can also potentially do.

That is not what I want to do. I want to regulate access to certain
FILES. I don't care about apache itself at this point. The scenario I
want to avoid is this:

/var/www/user1/script.php
/var/www/user2/script.php

where user2's script contains something like:
<? $f=fopen("../user1/script.php"); read($f); ?>




-- 
http://web.lemuria.org/pubkey.html
pub  1024D/D88D35A6 2001-11-14 Tom Vogt <tom@lemuria.org>
     Key fingerprint = 276B B7BB E4D8 FCCE DB8F  F965 310B 811A D88D 35A6

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.