From: Shane Wang <shane.wang@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "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: Tue, 29 Sep 2009 14:34:09 +0800 [thread overview]
Message-ID: <4AC1AA61.8070408@intel.com> (raw)
In-Reply-To: <20090928211745.GA2119@elf.ucw.cz>
Pavel Machek wrote:
> On Mon 2009-09-28 14:11:25, H. Peter Anvin wrote:
>> On 09/28/2009 02:07 PM, Rafael J. Wysocki wrote:
>>>> Well, I worry that S3 support for TXT makes TXT completely useless. A
>>>> little liquid nitrogen, remove RAM, place it in another machine,
>>>> modify it in any way you want, more liquid nitrogen, place it back.
>>>>
>>>> Oops, protection provided by TXT is lost.
>>> Ah, I see your point now.
>>>
>> Shane Wang sent me a patch for S3 support, but it missed the merge window:
>>
>> http://marc.info/?i=4A9CE0B2.5060608@intel.com
>>
>> *As far as I understand* -- and I haven't looked into it in detail yet,
>> having just come back from Plumber's -- this provides integrity
>> protection, not content extraction protection.
>
> How does it provide integrity protection? I'm free to modify RAM
> content in the other machine....
> Pavel
Hi Pavel,
Before S3 sleep, tboot patch will MAC the memory, and after S3 resume, the
memory integrity will be verified according to the MAC value. So, you can't
modify RAM, or else you will fail on S3 resume.
The current patch hpa mentioned is for userspace memory integrity. For kernel
memory integrity, the code is already in with the previous txt patch.
Thanks.
Shane
next prev parent reply other threads:[~2009-09-29 6:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 20:51 [GIT PULL] x86/txt for v2.6.32 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 [this message]
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
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=4AC1AA61.8070408@intel.com \
--to=shane.wang@intel.com \
--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=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;
as well as URLs for NNTP newsgroup(s).