All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@gentoo.org>
To: russell@coker.com.au
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
	SELinux <SELinux@tycho.nsa.gov>
Subject: Re: running interpreted scripts in different domains
Date: Mon, 19 Jul 2004 08:01:49 -0400	[thread overview]
Message-ID: <40FBB82D.1030909@gentoo.org> (raw)
In-Reply-To: <200407192156.56501.russell@coker.com.au>

Russell Coker wrote:

>On Mon, 19 Jul 2004 18:28, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>  
>
>>it sounds to me like you almost need to have _two_ contexts.
>>
>>one method_php_t and the other user_t.
>>
>>and to be able to make access decisions like this:
>>
>>	allow method_php_t+user_t bin_t:lnk_file file_read;
>>
>>meaning "if you have both the method_php_t context AND the user_t
>>context, then allow reading of symbolic links in /bin".
>>    
>>
>
>Currently in SE Linux each process has exactly one context, it can only gain a 
>new context by dropping the old one.  If a process could have two contexts 
>then it could potentially go through a series of operations to collect 
>multiple contexts ending up with a large set of access rights which were not 
>planned by the person who wrote the policy.  Some other security systems have 
>had problems similar to this.
>
>  
>
Right, fastcgi supports having multiple interpreters running (one per 
uid generally)

so the question is not to get the information to fastcgi about what 
context to put in setexeccon().


Joshua Brindle

--
This message was distributed to subscribers of the selinux mailing 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:[~2004-07-19 12:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18 20:33 running interpreted scripts in different domains Joshua Brindle
2004-07-19  8:28 ` Luke Kenneth Casson Leighton
2004-07-19 11:56   ` Russell Coker
2004-07-19 12:01     ` Joshua Brindle [this message]
2004-07-20 15:42 ` James Carter
2004-07-20 18:14   ` Joshua Brindle
2004-07-20 20:27     ` James Carter
2004-07-20 20:32       ` Joshua Brindle
2004-07-20 23:22         ` Luke Kenneth Casson Leighton
2004-07-21  0:59           ` Joshua Brindle
2004-07-21 23:06         ` Thomas Bleher
2004-07-22  8:56           ` Luke Kenneth Casson Leighton
2004-07-22 13:19             ` Daniel J Walsh
2004-07-22 14:35             ` Luke Kenneth Casson Leighton

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=40FBB82D.1030909@gentoo.org \
    --to=method@gentoo.org \
    --cc=SELinux@tycho.nsa.gov \
    --cc=lkcl@lkcl.net \
    --cc=russell@coker.com.au \
    /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.