public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: serue@us.ibm.com
Cc: James Morris <jmorris@redhat.com>,
	Reiner Sailer <sailer@watson.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	LSM <linux-security-module@wirex.com>,
	Tom Lendacky <toml@us.ibm.com>, Greg KH <greg@kroah.com>,
	Chris Wright <chrisw@osdl.org>, 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 13:59:26 -0700	[thread overview]
Message-ID: <20050615205926.GP9046@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050615204936.GA3517@serge.austin.ibm.com>

* serue@us.ibm.com (serue@us.ibm.com) wrote:
> Since IMA provides support for a new type of security policy,
> specifically remote system integrity verification, I don't see
> where LSM shouldn't necessarily be used.
> 
> I'm also curious about the current kernel development approach:
> On the one hand, when filesystem auditing was introduced, Christoph
> asked whether inotify and audit should be merged because they hook
> some of the same places.  Can someone reconcile these points of view
> for me, please?  If Reiner goes ahead and moves the IMA code straight
> into the kernel, does anyone doubt that he'll be asked to merge it
> with LSM?

The primary purpose of the hooks is access control.  Some of them, of
course, are helpers to keep labels coherent.  IIRC, James objected
because the measurement data was simply collected from these hooks.

  parent reply	other threads:[~2005-06-15 21:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 14:40 [PATCH] 3 of 5 IMA: LSM-based measurement code 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=20050615205926.GP9046@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=emilyr@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=jmorris@redhat.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