All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@gentoo.org>
To: SELinux <SELinux@tycho.nsa.gov>
Subject: running interpreted scripts in different domains
Date: Sun, 18 Jul 2004 16:33:22 -0400	[thread overview]
Message-ID: <40FADE92.7060307@gentoo.org> (raw)

Ok, so I had this seemingly good idea to let apache run interpreted apps 
(php, perl, whathaveyou) in different domains. To do this I started 
playing with fastcgi to do the type transition from apache to the 
interpreters domain (which works well) but that leaves all php scripts 
in the same domain (php_t) which then can't be isolated from one 
another. The idea is to have a php domain for each user (method_php_t) 
and so on. The only way I could think to do this was to use fastcgi's 
wrapper function to setexec() before calling the interpreter (it will do 
this per user). So the idea is that there is a php script of a user 
labeled with something like method_php_script_t and the fastcgi wrapper 
would read that target context and paired with it's source context ask 
selinux what the auto type trans would be so that it can explicitly do 
it with setexec().

The problem is that the userspace avc doesn't currently provide this 
information, all you can get is an access decision or a labeling or 
relabeling decision. It seems a little extreme to add a 
security_compute_trans() to the userspace avc (and selinuxfs filesystem, 
etc) just to make scripts a little more isolated and provide more fine 
grained access but I can't think of another (good) way to do this. The 
alternative would be to use default types but that isn't very scalable 
for X number of interpreters times N number of users.

Can anyone else think of a way to accomplish this or shall I try adding 
a calculate auto type trans to the userspace avc's?

Joshua Brindle
Hardened Gentoo

--
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-18 20:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18 20:33 Joshua Brindle [this message]
2004-07-19  8:28 ` running interpreted scripts in different domains Luke Kenneth Casson Leighton
2004-07-19 11:56   ` Russell Coker
2004-07-19 12:01     ` Joshua Brindle
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=40FADE92.7060307@gentoo.org \
    --to=method@gentoo.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.