Messages in this thread | | | Date | Tue, 29 Sep 2009 14:34:09 +0800 | From | Shane Wang <> | Subject | Re: [GIT PULL] x86/txt for v2.6.32 |
| |
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
| |