From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, casey@schaufler-ca.com
Cc: akpm@osdl.org, torvalds@osdl.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Version 9 (2.6.24-rc1) Smack: Simplified Mandatory Access Control Kernel
Date: Thu, 25 Oct 2007 11:58:58 -0700 (PDT) [thread overview]
Message-ID: <551347.37651.qm@web36604.mail.mud.yahoo.com> (raw)
In-Reply-To: <1193324834.2683.113.camel@moss-spartans.epoch.ncsc.mil>
--- Stephen Smalley <sds@tycho.nsa.gov> wrote:
> On Wed, 2007-10-24 at 20:46 -0700, Casey Schaufler wrote:
> ...
> > +Smack does not implement Domain Type Enforcement (DTE). If
> > +you want DTE Linux has an implementation called SELinux.
> > +Those who really want DTE are encouraged to use SELinux.
> > +Those who don't know what DTE is are encouraged to compare
> > +SELinux with Smack to determine which mechanisms are best
> > +suited to the problem at hand.
>
> Nit: SELinux does not implement DTE. DTE was a scheme introduced by Lee
> Badger et al to apply implicit typing based on pathname as a variant of
> the original type enforcement model. SELinux is an implementation of
> the Flask security architecture for flexible MAC, along with an example
> security server that implements RBAC, TE, and MLS models, but not
> limited to them.
Okey Dokey. I'll fix that up.
Thank you for the review. I will have a look at all of the
individual comments.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2007-10-25 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 3:46 [PATCH 2/2] Version 9 (2.6.24-rc1) Smack: Simplified Mandatory Access Control Kernel Casey Schaufler
2007-10-25 15:07 ` Stephen Smalley
2007-10-25 18:58 ` Casey Schaufler [this message]
2007-10-26 20:34 ` Stephen Smalley
2007-10-27 3:00 ` Ahmed S. Darwish
2007-10-27 19:20 ` Casey Schaufler
2007-10-27 9:01 ` Ahmed S. Darwish
2007-10-27 23:47 ` Al Viro
2007-10-28 5:41 ` Casey Schaufler
2007-10-28 12:46 ` Ahmed S. Darwish
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=551347.37651.qm@web36604.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=torvalds@osdl.org \
/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.