From: Seth Arnold <seth.arnold@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [Patch 1/1] IBAC Patch
Date: Wed, 14 Mar 2007 11:48:42 -0700 [thread overview]
Message-ID: <20070314184841.GJ27643@suse.de> (raw)
In-Reply-To: <1173871526.18147.3.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
On Wed, Mar 14, 2007 at 07:25:26AM -0400, Mimi Zohar wrote:
> It's a little bit of both. :-) Initially it was written to help me with
:)
> implementing and testing the integrity provider. But it could definitely stand
> on it's own. As Serge Hallyn commented http://lkml.org/lkml/2007/3/13/220, by
> adding the mmap hook, IBAC could replace the LSM aspect of digsig and a gpg
> based integrity provider, could be written, instead of EVM, which is TPM based.
Thanks.
> > > + if (status != INTEGRITY_PASS) { /* FAIL | NO_LABEL */
> > > + if (!is_kernel_thread(current)) {
> >
> > Please remind me why kernel threads are exempt?
>
> You really don't want to prevent kernel threads from working. Nasty things
> happen.
But under what conditions would a kernel thread not pass integrity? I
guess if it doesn't have an associated dentry... or the dentry refers
to something else? (What does knfsd do -- it is started by a userland
program which causes the kernel to start up some tasks for NFS..)
> For integrity_measure(), EVM calls IMA, if enabled, to extend the
> measurement list with the hash value it provides. In most cases, EVM
> has already calculated the hash value, when it was called to verify the
> data. integrity_measure() is not meant to be intrusive, so it is defined
> as void.
Oh, ok, thanks.
> Thank you for your comments.
My pleasure, thanks for the quick responses.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-14 18:48 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
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 [this message]
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=20070314184841.GJ27643@suse.de \
--to=seth.arnold@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).