From: Chris Wright <chris@wirex.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Extended Attributes for Security Modules
Date: Tue, 15 Apr 2003 11:56:34 -0700 [thread overview]
Message-ID: <20030415115634.A24178@figure1.int.wirex.com> (raw)
In-Reply-To: <200304151436_MC3-1-3487-2164@compuserve.com>; from 76306.1226@compuserve.com on Tue, Apr 15, 2003 at 02:33:53PM -0400
* Chuck Ebbert (76306.1226@compuserve.com) wrote:
> Stephen Smalley wrote:
>
> > In practice, I would
> > expect that any "stacking" of multiple security modules that use
> > security fields and xattr will actually involve creation of a new module
> > that integrates the logic of the individual modules. This is preferable
> > anyway to ensure that the interactions among the security modules are
> > well understood, that the logic is combined in a sensible manner, and
> > that the individual logics can not subvert one another.
>
> On FreeBSD 5 you 'stack' the mac_biba and mac_mls modules to get both
> integrity and confidentiality, right? Or is that something different?
It's a difference in implementation. FreeBSD builds stacking directly into
the framework, whereas LSM makes stacking a policy decision for the module.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2003-04-15 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 18:33 Chuck Ebbert
2003-04-15 18:56 ` Chris Wright [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-10 12:06 Stephen Smalley
2003-04-13 22:57 ` Andreas Gruenbacher
2003-04-15 13:41 ` Stephen Smalley
2003-04-15 16:58 ` richard offer
2003-04-15 18:19 ` Stephen Smalley
2003-04-16 13:47 ` Stephen Smalley
2003-04-16 22:02 ` richard offer
2003-04-17 4:24 ` Stephen Smalley
2003-04-17 20:30 ` Chris Wright
2003-04-17 20:53 ` richard offer
2003-04-18 1:07 ` Chris Wright
2003-04-08 20:26 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=20030415115634.A24178@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®