From: Colin Walters <walters@verbum.org>
To: jsingh@ensim.com
Cc: SELinux@tycho.nsa.gov
Subject: Re: writing rules to disallow a domain to read particular files
Date: Sat, 16 Oct 2004 13:40:13 -0400 [thread overview]
Message-ID: <1097948413.3872.3.camel@x-infinity.verbum.private> (raw)
In-Reply-To: <1097940101.2569.5.camel@jsingh.india.ensim.com>
On Sat, 2004-10-16 at 20:51 +0530, Jaspreet Singh wrote:
> Hi,
>
> can someone help me with writing policy rules such that -
>
> A domain (say apache_d) cannot access files beyond a directory
> /home/jaspreet/
Look at the label on /home/jaspreet. It should be user_home_dir_t. The
labels on contained files are user_home_t. If you allow httpd_t access
to user_home_dir_t, but not user_home_t, that should achieve your goal.
What is your higher level goal though?
> Also if anyone could explain the behavior of "newrole" how can that be
> used here.
It's not really relevant to your previous problem. Do you have a
specific question about newrole?
--
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.
next prev parent reply other threads:[~2004-10-16 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 15:21 writing rules to disallow a domain to read particular files Jaspreet Singh
2004-10-16 17:40 ` Colin Walters [this message]
2004-10-17 12:54 ` Jaspreet Singh
2004-10-17 14:14 ` Luke Kenneth Casson Leighton
2004-10-17 14:31 ` Jaspreet Singh
2004-10-17 15:01 ` Luke Kenneth Casson Leighton
2004-10-17 17:16 ` Chris Kuethe
2004-10-17 16:35 ` Colin Walters
2004-10-18 7:58 ` Jaspreet Singh
2004-10-18 13:18 ` Colin Walters
2004-10-18 15:38 ` Karl MacMillan
2004-10-18 9:41 ` Jaspreet Singh
2004-10-18 13:22 ` Stephen Smalley
2004-10-16 19:39 ` 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=1097948413.3872.3.camel@x-infinity.verbum.private \
--to=walters@verbum.org \
--cc=SELinux@tycho.nsa.gov \
--cc=jsingh@ensim.com \
/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.