From: Casey Schaufler <casey@schaufler-ca.com>
To: serue@us.ibm.com, Chris Wright <chrisw@osdl.org>
Cc: Tom Lendacky <toml@us.ibm.com>, Greg KH <greg@kroah.com>,
LSM <linux-security-module@wirex.com>,
LKML <linux-kernel@vger.kernel.org>,
Reiner Sailer <sailer@watson.ibm.com>,
Emily Rattlif <emilyr@us.ibm.com>,
Kylene Hall <kylene@us.ibm.com>
Subject: Re: [PATCH] 3 of 5 IMA: LSM-based measurement code
Date: Wed, 15 Jun 2005 15:00:32 -0700 (PDT) [thread overview]
Message-ID: <20050615220032.67977.qmail@web31612.mail.mud.yahoo.com> (raw)
In-Reply-To: <20050615215019.GB3660@serge.austin.ibm.com>
--- serue@us.ibm.com wrote:
> Ok, so to be clear, any module which does not
> directly impose some form
> of access control is not eligible for an LSM?
In particular, an additional access control.
LSM is not for changing the existing policy,
it is for imposing additional policy.
You could, of course, add code to act on the
integrity measurements you've made, in which
case you could be in conformance with the
stated eligibilty requirements.
> (in that case that clearly settles the issue)
It sure took the wind out of the sails for the
SGI audit implementation.
Casey Schaufler
casey@schaufler-ca.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2005-06-15 22:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 14:40 Reiner Sailer
2005-06-15 20:02 ` James Morris
2005-06-15 20:49 ` serue
2005-06-15 20:58 ` Stephen Smalley
2005-06-15 21:48 ` serue
2005-06-15 20:59 ` Chris Wright
2005-06-15 21:50 ` serue
2005-06-15 21:53 ` Chris Wright
2005-06-15 22:42 ` Serge E. Hallyn
2005-06-15 22:49 ` Chris Wright
2005-06-15 22:00 ` Casey Schaufler [this message]
2005-06-15 22:38 ` Serge E. Hallyn
2005-06-15 22:40 ` Chris Wright
2005-06-15 22:52 ` Serge E. Hallyn
2005-06-16 2:01 ` Chris Wright
2005-06-15 22:44 Reiner Sailer
2005-06-15 22:59 ` Chris Wright
2005-06-15 22:48 Reiner Sailer
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=20050615220032.67977.qmail@web31612.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=chrisw@osdl.org \
--cc=emilyr@us.ibm.com \
--cc=greg@kroah.com \
--cc=kylene@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sailer@watson.ibm.com \
--cc=serue@us.ibm.com \
--cc=toml@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®