From: Pavel Machek <pavel@suse.cz>
To: Chris Wright <chrisw@sous-sol.org>
Cc: "Cihula, Joseph" <joseph.cihula@intel.com>,
linux-kernel@vger.kernel.org, "Wang,
Shane" <shane.wang@intel.com>, "Wei, Gang" <gang.wei@intel.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Chris Wright <chrisw@redhat.com>,
Jan Beulich <jbeulich@novell.com>,
mingo@elte.hu, tytso@mit.edu
Subject: Re: [RFC][PATCH 0a/3] TXT: Intel(R) Trusted Execution Technology support for Linux - Overview
Date: Thu, 9 Oct 2008 20:21:49 +0200 [thread overview]
Message-ID: <20081009182149.GE12507@elf.ucw.cz> (raw)
In-Reply-To: <20081009181451.GD6912@sequoia.sous-sol.org>
On Thu 2008-10-09 11:14:51, Chris Wright wrote:
> * Pavel Machek (pavel@suse.cz) wrote:
> > I have never used trusted boot and I'm not sure I want to. Why would I
> > want to do that?
>
> So that you can reason that you've booted kernel/initrd that you wanted
> to (and have established a root of trust for follow-on, like Joe's IMA
> example), and in the case that you didn't (say bluepill), you have a
> policy in place to handle it.
So like... instead of booting into rootkit it now will not boot at
all?
> > You exit/reenter the trusted mode accross sleep... so any guarantees
> > "trusted" mode does are void, right?
>
> You exit from kernel to tboot on any shutdown, which handles the proper
> teardown of the measured env (meaning you also come back on via tboot).
> So things like saving tpm state, scrubbing secrets from memory, etc.
Aha, so instead sleep mode is useless because I'll have to remount all
the crypto filesystems and restart all the apps...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-10-09 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 20:34 [RFC][PATCH 0a/3] TXT: Intel(R) Trusted Execution Technology support for Linux - Overview Cihula, Joseph
2008-10-09 12:53 ` Pavel Machek
2008-10-09 17:44 ` Chris Wright
2008-10-09 17:59 ` Pavel Machek
2008-10-09 18:14 ` Chris Wright
2008-10-09 18:21 ` Pavel Machek [this message]
2008-10-09 18:35 ` [RFC][PATCH 0a/3] TXT: Intel(R) Trusted Execution Technologysupport " Cihula, Joseph
2008-10-09 18:45 ` Pavel Machek
2008-10-09 21:16 ` [RFC][PATCH 0a/3] TXT: Intel(R) Trusted ExecutionTechnologysupport " Cihula, Joseph
2008-10-09 18:37 ` [RFC][PATCH 0a/3] TXT: Intel(R) Trusted Execution Technology support " Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 22:46 Joseph Cihula
2008-10-08 7:24 ` Peter Zijlstra
2008-10-08 18:38 ` Joseph Cihula
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=20081009182149.GE12507@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=arjan.van.de.ven@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=chrisw@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=gang.wei@intel.com \
--cc=jbeulich@novell.com \
--cc=joseph.cihula@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shane.wang@intel.com \
--cc=tytso@mit.edu \
/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