public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: linux-kernel@vger.kernel.org
Cc: Theodore Tso <tytso@mit.edu>,
	Joseph Cihula <joseph.cihula@intel.com>,
	mingo@elte.hu, arjan@linux.intel.com, hpa@zytor.com,
	andi@firstfloor.org, chrisw@sous-sol.org, jmorris@namei.org,
	jbeulich@novell.com, peterm@redhat.com, gang.wei@intel.com,
	shane.wang@intel.com, John Gilmore <gnu@toad.com>
Subject: Re: [RFC v3][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support
Date: Thu, 14 May 2009 17:52:04 +0200	[thread overview]
Message-ID: <20090514155204.GA6273@fancy-poultry.org> (raw)
In-Reply-To: <20090512210154.GC23773@mit.edu>

On 13.05.2009, Theodore Tso wrote: 

> Ross Anderson was one of the first to write about these concerns, over
> five years ago:
> 
>      http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
> 
> It's interesting that his 2003 document was able to predict the
> emergence of the LaGrande Technology (see question 15 in the above
> FAQ).

Many thanks for pointing this out!

Strange enough, nobody seems to care. I have carefully read Ross Andersons
report, and I'm more than concerned now. Because I'm not a kernel
programmer, I can not see by myself what these patches will do to the Linux
kernel at all, so I can only hope that Linus will not let them in if they 
can be misused to what Ross Anderson describes in his paper.

Regards,
Heinz.

  reply	other threads:[~2009-05-14 15:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  4:49 [RFC v3][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support Joseph Cihula
2009-05-08  6:53 ` Andrew Morton
2009-05-29  1:02   ` Cihula, Joseph
2009-05-08  9:57 ` Ingo Molnar
2009-05-12  5:26   ` Cihula, Joseph
2009-05-12  9:45     ` Ingo Molnar
2009-05-12  9:55       ` Andi Kleen
2009-05-12 21:01 ` Theodore Tso
2009-05-14 15:52   ` Heinz Diehl [this message]
2009-05-15  0:17   ` James Morris
2009-05-15  1:45     ` Cihula, Joseph
2009-05-15  1:51       ` Joe Perches
2009-05-15  2:49         ` Cihula, Joseph
2009-05-28  1:12           ` James Morris
2009-05-15 12:07       ` Theodore Tso
2009-05-15 12:26         ` Theodore Tso
2009-05-24 19:42         ` Pavel Machek
2009-05-24 19:42       ` Pavel Machek
     [not found]         ` <E1M8kJQ-0000W3-TE@fencepost.gnu.org>
2009-05-26  2:31           ` Theodore Tso
     [not found]             ` <E1M9Mig-0003Q4-S1@fencepost.gnu.org>
2009-05-29  9:47               ` Pavel Machek
2009-05-19 20:30     ` Pavel Machek
2009-05-22 16:59       ` H. Peter Anvin

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=20090514155204.GA6273@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=chrisw@sous-sol.org \
    --cc=gang.wei@intel.com \
    --cc=gnu@toad.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=peterm@redhat.com \
    --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