All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@epoch.ncsc.mil>
To: Nick Gray <nick-lists@austin.rr.com>
Cc: SELinux ML <selinux@tycho.nsa.gov>
Subject: Re: Tomcat policy
Date: Thu, 16 Dec 2004 15:46:13 -0500	[thread overview]
Message-ID: <1103229973.1463.145.camel@moss-spartans.epoch.ncsc.mil> (raw)
In-Reply-To: <1103224127.32688.49.camel@hawaii.grays-systems.com>

On Thu, 2004-12-16 at 14:08, Nick Gray wrote:
> So why can't I use tomcat_t to label directories?

Because you have defined it as a domain, not a file type.  Domains are
for processes, and are also applied to the /proc/pid entries of that
process.  You aren't supposed to use them for other files, and the
filesystem associate permission check enforces the restriction.

You do need to label the entrypoint program for the daemon with
tomcat_exec_t.

> I think I understand how to protect the daemon from the system, how do I
> protect the system from the daemon.

Under targeted policy, the "system" (i.e. unconfined processes) can do
whatever it wants to the daemon.  By defining a domain for tomcat, you
are merely controlling what it can do to the system, and isolating it
from other confined domains.  The daemon (if you have set it up properly
to run in the tomcat_t domain) can only do what you allow tomcat_t to do
in the policy, nothing else.

-- 
Stephen Smalley <sds@epoch.ncsc.mil>
National Security Agency


--
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-12-16 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 19:08 Tomcat policy Nick Gray
2004-12-16 20:46 ` Stephen Smalley [this message]
2004-12-17 14:56   ` Nick Gray
2004-12-17 15:09     ` Stephen Smalley
2004-12-17 16:36       ` Nick Gray
2004-12-16 21:39 ` Colin Walters
2004-12-16 21:47   ` Stephen Smalley

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=1103229973.1463.145.camel@moss-spartans.epoch.ncsc.mil \
    --to=sds@epoch.ncsc.mil \
    --cc=nick-lists@austin.rr.com \
    --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.