The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: linux-kernel@vger.kernel.org, safford@watson.ibm.com,
	serue@linux.vnet.ibm.com, zohar@us.ibm.com, sailer@us.ibm.com
Subject: Re: [RFC][Patch 2/3]integrity: IMA as an integrity service provider
Date: Wed, 20 Jun 2007 10:48:43 -0400	[thread overview]
Message-ID: <1182350923.5688.27.camel@localhost.localdomain> (raw)
In-Reply-To: <Line.LNX.4.64.0706192217040.19316@localhost.localdomain>

On Tue, 2007-06-19 at 22:18 -0400, James Morris wrote:
> On Mon, 18 Jun 2007, Mimi Zohar wrote:
> 
> 
> > +/* what could we exclude
> > + *   - non-executable/non-library files ?
> > + *   - /proc /dev ?
> > + * Only measure files opened for read-only or execute
> > + */
> > +static int skip_measurement(struct inode *inode, int mask)
> > +{
> > +	if ((inode->i_sb->s_magic == PROC_SUPER_MAGIC) ||
> > +	    (inode->i_sb->s_magic == SYSFS_MAGIC)) {
> > +		return 1;	/*can't measure */
> > +	}
> 
> I'm pretty sure you should skip measurement for many more pseudo 
> filesystems than this.

The LSM module controls what is measured and should only be calling
integrity_measure() for appropriate files.  IBAC, for example, only
calls integrity_measure() for executables from bprm_check_security()
and file_mmap() and for other regular files from inode_permission(), 
based on the existence of the 'security.measure' xattr, which is 
labeled by a userspace application.  The integrity provider, here,
is just doing a quick sanity check, but I'll definitely make it 
more complete and fix the comment to make this clearer.

Thanks!

Mimi


      reply	other threads:[~2007-06-20 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 20:42 [RFC][Patch 2/3]integrity: IMA as an integrity service provider Mimi Zohar
2007-06-20  2:18 ` James Morris
2007-06-20 14:48   ` Mimi Zohar [this message]

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=1182350923.5688.27.camel@localhost.localdomain \
    --to=zohar@linux.vnet.ibm.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safford@watson.ibm.com \
    --cc=sailer@us.ibm.com \
    --cc=serue@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