From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Pavel Machek <pavel@ucw.cz>, James Morris <jmorris@namei.org>,
Joseph Cihula <joseph.cihula@intel.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, arjan@linux.intel.com,
hpa@zytor.com, andi@firstfloor.org,
Chris Wright <chrisw@sous-sol.org>,
jbeulich@novell.com, peterm@redhat.com, gang.wei@intel.com,
shane.wang@intel.com
Subject: Re: [RFC v4][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support
Date: Fri, 19 Jun 2009 20:11:59 +0100 [thread overview]
Message-ID: <20090619201159.35d259bb@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <33858.1245433922@turing-police.cc.vt.edu>
> "Somebody has screwed with this kernel image, and you're not booting what you
> thought you were booting."
So I screw with your user space - you can't measure enough to make it
save you in a general setup. Too much I can hit changes each boot.
For a tiny number of very special cases that are highly controlled it has
potential uses. Some of those are evil some are ones with meaningful uses
(eg ATM machines) - although attacks there have included hardware attacks
outside the PC components too.
Personally (and I'm sure Intel disagrees with me) my bigger work is that
I can't verify that the magic block of code for tboot is correct.
next prev parent reply other threads:[~2009-06-19 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 21:38 Joseph Cihula
2009-06-12 5:12 ` James Morris
2009-06-12 10:23 ` Andi Kleen
2009-06-19 15:05 ` Pavel Machek
2009-06-19 17:52 ` Valdis.Kletnieks
2009-06-19 19:11 ` Alan Cox [this message]
2009-06-19 20:27 ` Alan Cox
2009-06-22 1:33 ` James Morris
2009-06-19 21:22 ` Pavel Machek
2009-06-19 18:34 ` Chris Wright
2009-06-22 1:54 ` James Morris
2009-06-26 21:30 ` Pavel Machek
2009-06-28 22:46 ` James Morris
2009-08-24 9:43 ` 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=20090619201159.35d259bb@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=chrisw@sous-sol.org \
--cc=gang.wei@intel.com \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=jmorris@namei.org \
--cc=joseph.cihula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=peterm@redhat.com \
--cc=shane.wang@intel.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