From: Arjan van de Ven <arjan@infradead.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Pavel Machek <pavel@ucw.cz>, "Wang, Shane" <shane.wang@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"Cihula, Joseph" <joseph.cihula@intel.com>
Subject: Re: [GIT PULL] x86/txt for v2.6.32
Date: Sat, 3 Oct 2009 14:10:52 -0700 [thread overview]
Message-ID: <20091003141052.3767a371@infradead.org> (raw)
In-Reply-To: <20091003203619.GA27182@khazad-dum.debian.net>
On Sat, 3 Oct 2009 17:36:20 -0300
Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> On Sat, 03 Oct 2009, Pavel Machek wrote:
> > On Sat 2009-10-03 01:02:52, Wang, Shane wrote:
> > > > So I modify the RAM content so that BIOS does not think measured
> > > > environment existed before suspend?
> > > > Pavel
> > >
> > > Hi Pavel, what do you mean on this question?
> > > When do you modify the RAM? before S3 sleep?
> >
> > During the sleep, using something cold and second machine.
>
> And it is ridiculously easy to pull off, too:
> http://www.engadget.com/2008/02/21/cold-boot-disk-encryption-attack-is-shockingly-effective/
>
> Shows the attack being used to read sensitive keys, but you can use
> it also to *modify* system running state (it will be more difficult,
> as you need to remove and replace the RAM while on S3 instead of S5,
> but it should be doable by someone who knows what he is doing).
>
that assumes all state is in ram, and not some bit in the TPM..
(and as for that "we can steal the content"... that's confusing DRM
with TXT. TXT is integrity, DRM is. well evil ;-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-10-03 21:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 20:51 H. Peter Anvin
2009-09-26 9:56 ` Pavel Machek
2009-09-26 21:44 ` Rafael J. Wysocki
2009-09-28 21:02 ` Pavel Machek
2009-09-28 21:07 ` Rafael J. Wysocki
2009-09-28 21:11 ` H. Peter Anvin
2009-09-28 21:17 ` Pavel Machek
2009-09-29 6:34 ` Shane Wang
2009-09-29 17:13 ` Pavel Machek
2009-09-29 17:19 ` Arjan van de Ven
2009-09-30 2:16 ` Wang, Shane
2009-09-30 6:54 ` Pavel Machek
2009-10-02 17:02 ` Wang, Shane
2009-10-02 17:18 ` H. Peter Anvin
2009-10-03 15:00 ` Henrique de Moraes Holschuh
2009-10-03 20:19 ` Pavel Machek
2009-10-03 20:36 ` Henrique de Moraes Holschuh
2009-10-03 20:44 ` Roland Dreier
2009-10-06 8:12 ` Pavel Machek
2009-10-07 16:47 ` Cihula, Joseph
2009-10-17 19:28 ` Pavel Machek
2009-10-03 21:10 ` Arjan van de Ven [this message]
2009-10-03 21:56 ` Henrique de Moraes Holschuh
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=20091003141052.3767a371@infradead.org \
--to=arjan@infradead.org \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=joseph.cihula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=shane.wang@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®