linux-kernel - Re: [tpmdd-devel] [PATCH] tpm: Add sysfs interface to show TPM hardware version

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: <9f67321b-50bd-9e6f-61f8-c29ae14f261f@linux.vnet.ibm.com>
Date:   Tue, 14 Mar 2017 14:18:15 -0400
From:   Ken Goldman <kgold@...ux.vnet.ibm.com>
To:     linux-kernel@...r.kernel.org
Cc:     tpmdd-devel@...ts.sourceforge.net
Subject: Re: [tpmdd-devel] [PATCH] tpm: Add sysfs interface to show TPM
 hardware version

On 3/13/2017 3:10 AM, Peter Huewe wrote:

> And yes you are right there is currently no way, except for trial and
> error, for the userspace to determine this. So an interface to get
> this information makes sense to me.

In practice, I suspect that a single user space application won't
support both TPMs.  It will send the first command, get an error
response code that says it's the wrong TPM, and exit.

Note that, although there is no overlap in the command API, the packet
format is compatible enough that a meaningful response can be returned.