From: Murray McAllister <mmcallis@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: user guide draft: "SELinux Contexts and Attributes" review
Date: Wed, 03 Sep 2008 15:56:51 +1000 [thread overview]
Message-ID: <48BE2723.4030002@redhat.com> (raw)
In-Reply-To: <1220360324.26711.33.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Mon, 2008-09-01 at 17:03 +1000, Murray McAllister wrote:
>>> A process in one domain transitions to another domain by executing a new
>>> program with the entrypoint type for the new domain.
>> How about:
>>
>> A subject in one domain transitions to another domain by executing an
>> object that is labeled with a file type that has entrypoint permission
>> for the new domain. The entrypoint permission is used in SELinux policy,
>> and controls which domains an object can enter. The following example...
>
> Not exactly:
> 1) A new domain has entrypoint permission to the file type, not the
> other way around.
> 2) The entrypoint permission controls which programs can be used to
> enter a domain, not the other way around.
How about (from your original suggestion):
A subject in one domain transitions to another domain by executing an
object that has the entrypoint file type for the new domain. The
entrypoint permission is used in SELinux policy, and controls which
objects can be used to enter a domain.
I added the following to the list of steps:
An SELinux policy rule states that the passwd_t domain type has
entrypoint permission to the passwd_exec_t file type.
Thanks.
--
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.
prev parent reply other threads:[~2008-09-03 5:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 6:54 user guide draft: "SELinux Contexts and Attributes" review Murray McAllister
2008-08-27 13:47 ` Stephen Smalley
2008-09-01 7:03 ` Murray McAllister
2008-09-02 3:39 ` Murray McAllister
2008-09-02 4:48 ` Murray McAllister
2008-09-02 13:19 ` Stephen Smalley
2008-09-02 13:09 ` Stephen Smalley
2008-09-03 6:04 ` Murray McAllister
2008-09-03 13:01 ` Stephen Smalley
2008-09-05 5:46 ` Murray McAllister
2008-09-05 11:27 ` Stephen Smalley
2008-09-06 4:24 ` Murray McAllister
2008-09-08 0:44 ` Murray McAllister
2008-09-02 12:58 ` Stephen Smalley
2008-09-03 5:56 ` Murray McAllister [this message]
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=48BE2723.4030002@redhat.com \
--to=mmcallis@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.