mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Wang, Shane" <shane.wang@intel.com>, Pavel Machek <pavel@ucw.cz>,
	Arjan van de Ven <arjan@infradead.org>,
	"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 12:00:13 -0300	[thread overview]
Message-ID: <20091003150013.GD31552@khazad-dum.debian.net> (raw)
In-Reply-To: <4AC635D5.8080809@zytor.com>

On Fri, 02 Oct 2009, H. Peter Anvin wrote:
> On 10/02/2009 10:02 AM, Wang, Shane wrote:
> >> So I modify the RAM content so that BIOS does not think measured
> >> environment existed before suspend?
> > 
> > Hi Pavel, what do you mean on this question? 
> > When do you modify the RAM? before S3 sleep?
> > 
> 
> He was talking earlier about a liquid nitrogen freeze attack.

You wish one would need liquid nitrogen for it... frozen CO2 (dry ice) is
more than cold enough for such an attack, and _MUCH_ easier to both acquire
and handle than liquid nitrogen.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2009-10-03 15:00 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 [this message]
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
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=20091003150013.GD31552@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=arjan@infradead.org \
    --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®