From: Kylene Jo Hall <kjhall@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
LSM ML <linux-security-module@vger.kernel.org>
Cc: Dave Safford <safford@us.ibm.com>, Mimi Zohar <zohar@us.ibm.com>,
Serge Hallyn <sergeh@us.ibm.com>
Subject: [RFC][PATCH 0/6] Integrity Service and SLIM
Date: Fri, 14 Jul 2006 10:24:23 -0700 [thread overview]
Message-ID: <1152897864.23584.3.camel@localhost.localdomain> (raw)
This is an updated request for comments on a proposed integrity
service framework and dummy provider, along with SLIM, a low
water-mark mandatory access control LSM module which utilizes the
integrity services as additional input to the access control decisions.
The latest fixes include:
- SLIM: Locking overhaul
- All: Update to 2.6.18-rc1 kernel
Later we will be submitting EVM as a specific integrity service
provider under this proposed framework. By separating the submissions,
we hope that the integrity framework and its relationship to SLIM
(and potentially to selinux) will be clearer and easier to review.
Since this integrity provider is a dummy, it has no requirements for
TPM hardware, or for LSM stacking, again making the review simpler.
A corresponding userspace utility package is available at
http://www.research.ibm.com/gsal/tcpa
Patch 1/6 is a tiny patch to make mprotect available for revocation
Patch 2/6 provides the integrity service API with dummy provider.
Patch 3-6 provide SLIM, and a more detailed description of
its changes, and points out its use of the integrity service.
These patches have no prerequisites for stacker or TPM related patches.
next reply other threads:[~2006-07-14 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 17:24 Kylene Jo Hall [this message]
2006-07-24 17:51 Kylene Jo Hall
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=1152897864.23584.3.camel@localhost.localdomain \
--to=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@us.ibm.com \
--cc=sergeh@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
Powered by JetHome