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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080812193031.GD18034@infradead.org>
Date:	Tue, 12 Aug 2008 15:30:31 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Mimi Zohar <zohar@...ibm.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	James Morris <jmorris@...ei.org>, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	Randy Dunlap <randy.dunlap@...cle.com>, safford@...son.ibm.com,
	sailer@...son.ibm.com, Stephen Smalley <sds@...ho.nsa.gov>,
	serue@...ux.vnet.ibm.com, Al Viro <viro@...IV.linux.org.uk>,
	Debora Velarde <debora@...ux.vnet.ibm.com>,
	Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	Kenneth Goldman <kgold@...son.ibm.com>
Subject: Re: [PATCH 1/4] integrity: TPM internel kernel interface

On Mon, Aug 11, 2008 at 05:13:51PM -0400, Mimi Zohar wrote:
> 
> I assume the concern here is that between looking up the chip and actually 
> 
> using the chip, the TPM chip is disabled/deactivated.  Based on 
> discussions 
> with Kenneth Goldman, the TCG main specification part2: structures, 
> require
> that even if the TPM is disabled/deactivated, the command to extend the 
> PCR 
> will succeed, but the command to read the PCR will fail with an 
> appropriate 
> error code.

And what happens when the chip simply goes away due to a hotplug action?
Or not even the actual chip goes away but just the chip driver and you
now dereference freed memory?

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ