mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reiner Sailer <sailer@us.ibm.com>
To: serue@us.ibm.com
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	James Morris <jmorris@redhat.com>,
	Toml@us.ibm.com, Greg KH <greg@kroah.com>,
	LKML <linux-kernel@vger.kernel.org>,
	LSM <linux-security-module@wirex.com>,
	Chris Wright <chrisw@osdl.org>,
	Reiner Sailer <sailer@watson.ibm.com>,
	Emilyr@us.ibm.com, Kylene@us.ibm.com
Subject: Re: [PATCH] 3 of 5 IMA: LSM-based measurement code
Date: Wed, 15 Jun 2005 18:48:56 -0400 (Eastern Daylight Time)	[thread overview]
Message-ID: <Pine.WNT.4.63.0506151844370.2452@laptop> (raw)


Serge E. Hallyn (serue@us.ibm.com) wrote:
>
> That's true, of course.  Reiner, would any of the integrity measurement
> hooks be moved to a better place than the current LSM hooks?  Is there a
> preferred ordering - ie measurement should always happen before the LSM
> modules, or always after?  Either of these would of course be clear
> reasons to separate IMA into its own subsystem.
> 
> thanks,
> -serge

Originally, IMA was not an LSM. However, when moving to a 2.6 kernel, we 
moved it to LSM and have found very easily the current hooks. I don't think 
the hook position would change when moving from LSM to non-LSM.

Thanks
Reiner


             reply	other threads:[~2005-06-15 22:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 22:48 Reiner Sailer [this message]
  -- 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 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
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

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=Pine.WNT.4.63.0506151844370.2452@laptop \
    --to=sailer@us.ibm.com \
    --cc=Emilyr@us.ibm.com \
    --cc=Kylene@us.ibm.com \
    --cc=Toml@us.ibm.com \
    --cc=chrisw@osdl.org \
    --cc=greg@kroah.com \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=sailer@watson.ibm.com \
    --cc=sds@tycho.nsa.gov \
    --cc=serue@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®