From: guttman@mitre.org (Joshua D. Guttman)
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: "John D. Ramsdell" <ramsdell@mitre.org>,
Karl MacMillan <kmacmillan@tresys.com>,
selinux@tycho.nsa.gov, Amy L Herzog <aherzog@mitre.org>,
guttman@mitre.org (Joshua D. Guttman)
Subject: Re: Fedora Core 2 setools RPM
Date: 18 Jun 2004 15:31:09 -0400 [thread overview]
Message-ID: <nhabrjg3bpe.fsf@malabar.mitre.org> (raw)
In-Reply-To: <1087584215.27697.173.camel@moss-spartans.epoch.ncsc.mil>
Steve --
So in some sense the bottom line is that you think the type relations
give the essential core of the policy info, and to a first
approximation one can focus on that.
Of course, it's still desirable to have access to the supplementary
information (and an idea how to interpret it) so that the further
refinement will eventually work out.
A different point is that the main value added of slat is much more
expressive security goals (even when restricted to the types info).
You're not just talking about accessibility of a type to information
flow from another, but also whether all the possible flows go through
a desired gate type. And the key fact you mentioned at the end of
your last message
Stephen Smalley <sds@epoch.ncsc.mil> writes:
> But from an information flow perspective, you simply want to prove
> that user_t can only reach sysadm_t through specific gate domains
> like newrole_t.
is of this form: It's apparently not expressible as a simple
information flow accessibility assertion.
Cheers --
Joshua
--
Joshua D. Guttman <guttman@mitre.org>
MITRE, Mail Stop S119 Office: +1 781 271 2654
202 Burlington Rd. Fax: +1 781 271 8953
Bedford, MA 01730-1420 USA Cell: +1 781 526 5713
--
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-06-18 19:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 21:07 Fedora Core 2 policy source Kratzer, James R.
2004-06-15 23:26 ` Fedora Core 2 setools RPM John D. Ramsdell
2004-06-16 13:37 ` Stephen Smalley
2004-06-16 16:58 ` Daniel J Walsh
2004-06-17 9:47 ` SE Linux enhanced strace for Fedora Core 2 John D. Ramsdell
2004-06-17 15:36 ` Fedora Core 2 setools RPM Karl MacMillan
2004-06-17 15:58 ` Stephen Smalley
2004-06-17 18:47 ` Karl MacMillan
2004-06-18 13:00 ` John D. Ramsdell
2004-06-18 14:13 ` Stephen Smalley
2004-06-18 17:26 ` Joshua D. Guttman
2004-06-18 17:51 ` Stephen Smalley
2004-06-18 18:18 ` Joshua D. Guttman
2004-06-18 18:43 ` Stephen Smalley
2004-06-18 19:31 ` Joshua D. Guttman [this message]
2004-06-18 20:09 ` Stephen Smalley
2004-06-21 13:16 ` Frank Mayer
2004-06-21 13:14 ` Frank Mayer
2004-06-21 13:43 ` Joshua D. Guttman
2004-06-21 15:26 ` Frank Mayer
2004-06-21 15:28 ` Frank Mayer
2004-06-19 5:33 ` Russell Coker
2004-06-19 13:09 ` Serge E. Hallyn
2004-06-18 13:09 ` John D. Ramsdell
2004-06-21 13:04 ` Frank Mayer
2004-06-21 15:43 ` John D. Ramsdell
2004-06-17 18:31 ` John D. Ramsdell
2004-06-15 23:33 ` Fedora Core 2 policy source John D. Ramsdell
2004-06-16 1:25 ` John D. Ramsdell
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=nhabrjg3bpe.fsf@malabar.mitre.org \
--to=guttman@mitre.org \
--cc=aherzog@mitre.org \
--cc=kmacmillan@tresys.com \
--cc=ramsdell@mitre.org \
--cc=sds@epoch.ncsc.mil \
--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.