From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Casey Schaufler <casey@schaufler-ca.com>,
linux-kernel@vger.kernel.org, safford@watson.ibm.com,
serue@linux.vnet.ibm.com, kjhall@linux.vnet.ibm.com,
zohar@us.ibm.com
Subject: Re: [RFC][Patch 1/6] integrity: new hooks
Date: Thu, 08 Mar 2007 16:57:24 -0500 [thread overview]
Message-ID: <1173391044.5981.11.camel@localhost.localdomain> (raw)
In-Reply-To: <200703082038.l28Kcowq023278@turing-police.cc.vt.edu>
On Thu, 2007-03-08 at 15:38 -0500, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 08 Mar 2007 12:46:47 CST, "Serge E. Hallyn" said:
> > I think it should be done as both. The part which measures the
> > integrity of files should be an integrity subsystem. The part which
> > uses those results to either allow/refuse actions or take some other
> > action (i.e. shut down the system) should be an lsm.
>
> That would be good - the allow/deny parts, being security, can use the
> existing LSM hooks, and the integrity part can use the LIM hooks.
>
> Umm... wait a minute - *what* Linux Integrity Module hooks? :)
Hm, integrity-service-api-and-dummy-provider.patch contains:
integrity_verify_metadata, integrity_verify_data, and integrity_measure,
which could be referred to as either LIM hooks or as the API. This patch
set adds 8 new LIM hooks.
Mimi Zohar
prev parent reply other threads:[~2007-03-08 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 16:03 Mimi Zohar
2007-03-08 16:31 ` Chris Wright
2007-03-08 17:00 ` Serge E. Hallyn
2007-03-08 17:17 ` Chris Wright
2007-03-08 18:30 ` Casey Schaufler
2007-03-08 18:42 ` Chris Wright
2007-03-08 18:46 ` Serge E. Hallyn
2007-03-08 20:38 ` Valdis.Kletnieks
2007-03-08 20:54 ` Serge E. Hallyn
2007-03-08 21:57 ` Mimi Zohar [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=1173391044.5981.11.camel@localhost.localdomain \
--to=zohar@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=casey@schaufler-ca.com \
--cc=kjhall@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.com \
--cc=serue@linux.vnet.ibm.com \
--cc=serue@us.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
all inboxes | Powered by JetHome®