linux-kernel - Re: [tpmdd-devel] TPM chip prevents machine from suspending

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1301514238.561.9.camel@unknown001a4b0c2895>
Date:	Wed, 30 Mar 2011 15:43:58 -0400
From:	Eric Paris <eparis@...hat.com>
To:	Stefan Berger <stefanb@...ux.vnet.ibm.com>
Cc:	Rajiv Andrade <srajiv@...ux.vnet.ibm.com>,
	tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [tpmdd-devel] TPM chip prevents machine from suspending

On Tue, 2011-03-29 at 11:03 -0400, Stefan Berger wrote:

> - send  a command to the TPM upon resume and if TPM response returns 
> with error code 38 set a flag and don't send TPM_SaveState() upon the 
> next suspend; log this case; the TPM becomes unusable; machine will 
> suspend a 2nd time

I assume there is no reasonable way to detect this particular piece of
broken BIOS/hardware?  If not I think this sounds like the best option
to me.  If the TPM doesn't work after resume not much we can do other
than accept it doesn't work and move along.....

--
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/