tcti_socket: Move simulator initialization code into the context init function.

This is something that every application has to do to be sure that the
simulator has been initialized. Running these commands multiple time has
no negative effect (AFAIK). Might as well just run this each time we
initialize a connection to the simulator. Save everyone else the
headache.

Signed-off-by: Philip Tricca <philip.b.tricca@intel.com>
4 files changed
tree: f31ada9ae49337e11308ff2bcd041065f0f46ba9
  1. common/
  2. doc/
  3. include/
  4. lib/
  5. resourcemgr/
  6. sysapi/
  7. tcti/
  8. test/
  9. .gitattributes
  10. .gitignore
  11. bootstrap
  12. ChangeLog
  13. configure.ac
  14. INSTALL
  15. LICENSE
  16. Makefile.am
  17. README.md
  18. tss.sln
  19. tss.vcxproj
README.md

TPM (Trusted Platform Module) 2.0 Software Stack (TSS):

This stack consists of the following layers from top to bottom:

  • Feature API (FAPI), see specification 0.12, (published but still in progress and unimplemented)
  • Enhanced System API (ESAPI), (specification in progress and unimplemented)
  • System API (SAPI), see 1.0 specification, (public, 0.97 implementation complete). This layer implements the system layer API level of the TSS 2.0 specification. These functions can be used to access all TPM 2.0 functions as described in Part 3 of the TPM 2.0 specification. The usefulness of this code extends to all users of the TPM, even those not planning to use the upper layers of the TSS.
  • TPM Command Transmission Interface (TCTI), used by SAPI to communicate with next lower layer (either the TAB/RM or TPM 2.0 device driver), see SAPI specification
  • Trusted Access Broker/Resource Manager (TAB/RM), see 0.91 specification, (public, implementation complete). This layer sits between the system API library code and the TPM. It is a daemon that handles all multi-process coordination and manages the TPM's internal resources transparently to applications.

Since the FAPI and ESAPI haven't been implemented yet, this repository only contains the SAPI and layers below it, plus a test application for exercising the SAPI.

The test application, tpmclient, tests many of the commands against the TPM 2.0 simulator. The tpmclient application can be altered and used as a sandbox to test and develop any TPM 2.0 command sequences, and provides an excellent development and learning vehicle.

Build and Installation Instructions:

Run Instructions

Architecture/Block Diagram

Code Layout

Resources

TPM 2.0 specifications can be found at Trusted Computing Group.