From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Mimi Zohar <zohar@linux.vnet.ibm.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, 8 Mar 2007 12:46:47 -0600 [thread overview]
Message-ID: <20070308184646.GC21099@sergelap.austin.ibm.com> (raw)
In-Reply-To: <33939.11500.qm@web36612.mail.mud.yahoo.com>
Quoting Casey Schaufler (casey@schaufler-ca.com):
>
> --- "Serge E. Hallyn" <serue@us.ibm.com> wrote:
>
>
> > It's unfortunate, agreed, but
> >
> > use of LSM as an integrity framework was also a
> > no-go.
>
> You're going to have to justify this assertion.
You misunderstand. I wasn't saying it wouldn't work :) I was saying
that it's been said repeatedly that evm should be implemented as an
integrity, not security, module.
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.
> I know of at least one work-in-progress for which
> LSM works just fine. Not to mention the Integrity
> claims of SELinux.
-serge
next prev parent reply other threads:[~2007-03-08 18:48 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 [this message]
2007-03-08 20:38 ` Valdis.Kletnieks
2007-03-08 20:54 ` Serge E. Hallyn
2007-03-08 21:57 ` 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=20070308184646.GC21099@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--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=zohar@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
all inboxes | Powered by JetHome®