mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Reiner Sailer <sailer@us.ibm.com>
Cc: Valdis.Kletnieks@vt.edu, James Morris <jmorris@redhat.com>,
	Toml@us.ibm.com, linux-security-module@wirex.com,
	linux-kernel@vger.kernel.org, Emilyr@us.ibm.com,
	Kylene@us.ibm.com
Subject: Re: [PATCH 2 of 4] ima: related Makefile compile order change and Readme
Date: Mon, 23 May 2005 22:39:29 +0200	[thread overview]
Message-ID: <20050523203929.GA1940@elf.ucw.cz> (raw)
In-Reply-To: <Pine.WNT.4.63.0505231351590.4028@laptop>

Hi!

> > > Perhaps I don't understand things fully, but what is the purpose of 
> > > providing measurement values locally via proc?
> > > 
> > > How can they be trusted without the TPM signing an externally generated 
> > > nonce?
> > 
> > If you can't trust what the kernel is outputting in /proc, you're screwed.
> 
> No, this is not the case. You can establish trust into the measurements 
> read through /proc by validating the TPM signature over the measurement 
> aggregate on a separate, trusted system. IMA measurements are not intended 
> to be used on the local system but on a separate system that is trusted not 
> to be compromised. The system validating the measurements does not
> trust 

Actually, you "could" also cat /proc files, then verify the signature
by hand (using pen and paper :-).

It seems to me that the mechanism is sound... it does what the docs
says. Another questions is "is it usefull"?

								Pavel 


  reply	other threads:[~2005-05-23 20:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 19:56 Reiner Sailer
2005-05-23 20:39 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25 15:32 Reiner Sailer
2005-05-25 21:58 ` Pavel Machek
2005-05-25 15:00 Reiner Sailer
2005-05-25 15:06 ` Pavel Machek
2005-05-24 21:17 Reiner Sailer
2005-05-24 22:41 ` Pavel Machek
2005-05-24 13:45 Reiner Sailer
2005-05-24 18:47 ` Pavel Machek
2005-05-23 21:36 Reiner Sailer
2005-05-23 23:44 ` Pavel Machek
2005-05-23 23:59 ` James Morris
2005-05-25 18:06   ` Reiner Sailer
2005-05-22 23:59 Reiner Sailer
2005-05-23  4:30 ` James Morris
2005-05-23  4:52   ` Valdis.Kletnieks
2005-05-23  8:58 ` Pavel Machek
2005-05-20 13:36 Reiner Sailer
2005-05-21  6:02 ` Greg KH
2005-05-22 19:37 ` Pavel Machek

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=20050523203929.GA1940@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Emilyr@us.ibm.com \
    --cc=Kylene@us.ibm.com \
    --cc=Toml@us.ibm.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=sailer@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

Powered by JetHome