| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 3 Jul 2009 01:15:23 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: joseph.cihula@...el.com Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, arjan@...ux.intel.com, hpa@...or.com, andi@...stfloor.org, chrisw@...s-sol.org, jmorris@...ei.org, jbeulich@...ell.com, peterm@...hat.com, gang.wei@...el.com, shane.wang@...el.com Subject: Re: [RFC v6][PATCH 3/4] intel_txt: Intel(R) TXT Sx shutdown support On Wednesday 01 July 2009, Joseph Cihula wrote: > Support for graceful handling of sleep states (S3/S4/S5) after an Intel(R) TXT launch. > > Without this patch, attempting to place the system in one of the ACPI sleep > states (S3/S4/S5) To be precise, S5 is not a sleep state. > will cause the TXT hardware to treat this as an attack and > will cause a system reset, with memory locked. Not only may the subsequent > memory scrub take some time, but the platform will be unable to enter the > requested power state. > > This patch calls back into the tboot so that it may properly and securely clean > up system state and clear the secrets-in-memory flag, after which it will place > the system into the requested sleep state using ACPI information passed by the kernel. Is there any documentation describing how ACPI sleeps states are supposed to work with the TXT hardware? Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists