build: Move all distributed headers into a common directory.

The end goal of this work is to make the include directives in our
source code consistent with the layout that consuming applications will
have. This isn't so important for the library code, but for the test /
client / common code we've built up it is. This is the first step in a
larger effort to cleanup the compiler search paths we've had to set in
the build and to ease some of the cleanup that needs to be done over in
the tpm2.0-tools repo.

This is part of issue #93.

Signed-off-by: Philip Tricca <philip.b.tricca@intel.com>
20 files changed
tree: 112c4280ea82562f419bf68ca4e0859397e9b42a
  1. common/
  2. include/
  3. resourcemgr/
  4. sysapi/
  5. tcti/
  6. test/
  7. .gitattributes
  8. .gitignore
  9. arch.md
  10. archandlayout.md
  11. bootstrap
  12. buildwindows.md
  13. ChangeLog
  14. configure.ac
  15. INSTALL
  16. layout.md
  17. LICENSE
  18. Makefile.am
  19. README.md
  20. run.md
  21. simulator.md
  22. TSS block diagram.png
  23. TSS layout.png
  24. tss.sln
  25. 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.