public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: david safford <safford@watson.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, serue@linux.vnet.ibm.com,
	sailer@watson.ibm.com, zohar@us.ibm.com,
	Stephen Smalley <sds@tycho.nsa.gov>,
	CaseySchaufler <casey@schaufler-ca.com>
Subject: Re: [RFC][Patch 5/5]integrity: IMA as an integrity service provider
Date: Tue, 5 Aug 2008 19:32:09 +0200	[thread overview]
Message-ID: <20080805173208.GA8380@ucw.cz> (raw)
In-Reply-To: <1214324930.3262.94.camel@localhost.localdomain>

On Tue 2008-06-24 12:28:50, david safford wrote:
> On Wed, 2008-05-28 at 01:22 -0700, Andrew Morton wrote:
> 
> > - I see lots of user file I/O being done from within the kernel. 
> >   This makes eyebrows raise.  Also some other eyebrow-raising
> >   file-related things in there.
> > 
> > Generally: the code is all moderately intrusive into the VFS and this
> > sort of thing does need careful explanation and justification, please. 
> > Once we have some understanding of what you're trying to achieve here
> > we will inevitably ask "can't that be done in userspace".  So it would
> > be best if your description were to preemptively answer all that.  
> > 
> > 
> Sorry about this delayed response - we are about to repost for RFC, and
> noticed we missed responding to this.
> 
> The Trusted Computing (TPM) model requires that all files be measured,
> (hashed) and the measurement committed to the hardware TPM before any
> data of the file is accessed in any way. In addition, if the measurement
> is incorrect, all access to the file must be denied. 

TPM model may require this, but what is the benefit to the user/owner
of the machine?

							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-08-05 17:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 15:05 [RFC][Patch 5/5]integrity: IMA as an integrity service provider Mimi Zohar
2008-05-23 23:30 ` Randy Dunlap
2008-05-27  1:02   ` Mimi Zohar
2008-05-27 14:36   ` Mimi Zohar
2008-06-11 22:31     ` Randy Dunlap
2008-05-28  8:22 ` Andrew Morton
2008-05-29  3:17   ` Mimi Zohar
2008-05-29  3:30     ` Andrew Morton
2008-05-29 21:50       ` Mimi Zohar
2008-05-29 23:35         ` Andrew Morton
2008-05-30  1:58           ` Mimi Zohar
2008-05-30  2:04             ` Andrew Morton
2008-05-30 13:06       ` Mimi Zohar
2008-05-29  3:33   ` Mimi Zohar
2008-05-31  7:54   ` Pavel Machek
2008-06-24 16:28     ` david safford
2008-08-05 17:35       ` Pavel Machek
2008-06-24 16:28   ` david safford
2008-08-05 17:32     ` Pavel Machek [this message]
     [not found] <20080627131946.225566613@linux.vnet.ibm.com>
2008-06-27 16:23 ` [RFC][PATCH 5/5] integrity: " 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=20080805173208.GA8380@ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=casey@schaufler-ca.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safford@watson.ibm.com \
    --cc=sailer@watson.ibm.com \
    --cc=sds@tycho.nsa.gov \
    --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