All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: policy question
Date: Fri, 19 Apr 2002 08:14:35 +0200	[thread overview]
Message-ID: <20020419081435.C11674@lemuria.org> (raw)
In-Reply-To: <20020418214440.887A644E3E@lyta.coker.com.au>; from russell@coker.com.au on Thu, Apr 18, 2002 at 11:44:40PM +0200

On Thu, Apr 18, 2002 at 11:44:40PM +0200, Russell Coker wrote:
> > You have me lost here. If I allow a specific, controlled domain
> > transition, how does that open up all domains to an attacker?
> 
> If we have 10 users with 10 different domains and allow Apache to change 
> between them (forward and backward) at will, then anything which compromises 
> Apache or any of it's scripts can get any of the domains.  In which case why 
> not just save yourself the trouble and use a single domain.

I see two scenarios:

1) Apache itself is compromised. In that case, you are where you are
right now, namely that the attacker has all the rights that apache has.
Nothing gained, but nothing lost, either.

2) A single script gets compromised. In that case, the attacker is in a
tiny domain that allows access to only one user's files. That's a huge
gain, and this danger is many times higher than the other one.

There would be no transition between user domains. The transitions
allowed would be from apache to a user and from a user to apache. The
later would happen on exit. As long as your script is still doing
stuff, you are in the user domain.


> > None of which would have been possible if there had been a tight domain
> > for the PHP script to run in.
> 
> But a tight domain for PHP is impossible while PHP is essentially part of 
> Apache.  To have a tight domain for PHP then you need to run it as a cgi-bin 
> program using suexec.

All this was to find out whether it is possible with SELinux to have
the cake (module) and eat it, too (have security). Looks like it isn't.


> The problem is that the kernel doesn't know what the application is trying to 
> do with each file.

It doesn't have to. All it needs is to understand that it opens a file,
which it does understand pretty well, and that if that file has a
certain label, it needs to make a domain transition. That is apparently
the point it doesn't "get", so I'll have to look for a different way of
doing things.


-- 
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.

  reply	other threads:[~2002-04-19  6:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  9:22 policy question Tom
2002-04-18 10:44 ` Russell Coker
2002-04-18 12:25   ` Tom
2002-04-18 14:51     ` Russell Coker
2002-04-18 15:15       ` Tom
2002-04-18 15:32         ` Stephen Smalley
2002-04-18 16:21           ` Tom
2002-04-18 18:28             ` Russell Coker
2002-04-18 20:40               ` Tom
2002-04-18 21:47                 ` Russell Coker
2002-04-19  6:30                   ` Tom
2002-04-18 16:08         ` Russell Coker
2002-04-18 16:32           ` Tom
2002-04-18 18:47             ` Russell Coker
2002-04-18 20:49               ` Tom
2002-04-18 21:44                 ` Russell Coker
2002-04-19  6:14                   ` Tom [this message]
2002-04-19  9:10                     ` Russell Coker
2002-04-19 12:27                       ` Tom
2002-04-19 15:02             ` Stephen Smalley
2002-04-18 15:22 ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2002-05-02 10:11 Policy question Reino Wallin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020419081435.C11674@lemuria.org \
    --to=tom@lemuria.org \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.