From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-security-module@vger.kernel.org, safford@watson.ibm.com,
serue@linux.vnet.ibm.com, kjhall@linux.vnet.ibm.com,
zohar@us.ibm.com, linux-kernel@vger.kernel.org,
disec-devel@lists.sourceforge.net
Subject: Re: [RFC] [Patch 1/1] IBAC Patch
Date: Mon, 12 Mar 2007 17:47:20 -0400 [thread overview]
Message-ID: <1173736041.5803.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200703090319.l293JrpC009714@turing-police.cc.vt.edu>
On Thu, 2007-03-08 at 22:19 -0500, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 08 Mar 2007 17:58:16 EST, Mimi Zohar said:
> > This is a request for comments for a new Integrity Based Access
> > Control(IBAC) LSM module which bases access control decisions
> > on the new integrity framework services.
> >
> > (Hopefully this will help clarify the interaction between an LSM
> > module and LIM module.)
>
> OK, between this and the additional LIM hooks I didn't notice in an earlier
> patch, we're starting to see the API. The only problem is that although
> it may be the right API for *your* code, I suspect it's a non-starter without
> a discussion about whether it's the right *generic* API for an LIM (which will
> require at least one dramatic bun fight about what "Integrity" means).
Absolutely, we need to make sure that the set of LIM hooks is complete and that
nothing is missing in order to implement different types of LIM providers. I'm
copying the digsig mailing list for their input on requirements, which this API
might not satisfy or perhaps address.
> > Index: linux-2.6.21-rc3-mm2/security/ibac/Kconfig
>
> Minor congnitive-dissonance alert:
>
> > +config SECURITY_IBAC_BOOTPARAM
> > + bool "IBAC boot parameter"
> > + depends on SECURITY_IBAC
> > + default y
>
> > + If you are unsure how to answer this question, answer N.
>
> The 'default' should in general match the hint we give the user.
Oops, blush. It will obviously be corrected in the next IBAC patch
release.
Mimi Zohar
next prev parent reply other threads:[~2007-03-12 22:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 22:58 [RFC] [Patch 1/1] IBAC Patch Mimi Zohar
2007-03-08 23:08 ` Randy Dunlap
2007-03-09 13:19 ` Mimi Zohar
2007-03-09 18:26 ` Randy Dunlap
2007-03-09 3:19 ` Valdis.Kletnieks
2007-03-09 15:07 ` Serge E. Hallyn
2007-03-12 21:47 ` Mimi Zohar [this message]
2007-03-13 15:31 ` Serge E. Hallyn
2007-03-14 9:46 ` Mimi Zohar
2007-03-14 2:27 ` Seth Arnold
2007-03-14 11:25 ` Mimi Zohar
2007-03-14 18:48 ` Seth Arnold
-- strict thread matches above, loose matches on Subject: below --
2007-03-14 9:49 Mimi Zohar
2007-06-18 20:48 [RFC][Patch " Mimi Zohar
2007-06-19 22:23 ` Serge E. Hallyn
2007-06-20 11:52 ` Mimi Zohar
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=1173736041.5803.3.camel@localhost.localdomain \
--to=zohar@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=disec-devel@lists.sourceforge.net \
--cc=kjhall@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@watson.ibm.com \
--cc=serue@linux.vnet.ibm.com \
--cc=zohar@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox