commit | 850bb59f8bb9464f992fa8376923a3baf266fdc5 | [log] [tgz] |
---|---|---|
author | Philip Tricca <philip.b.tricca@intel.com> | Tue Apr 03 09:29:22 2018 -0700 |
committer | Philip Tricca <philip.b.tricca@intel.com> | Tue Apr 03 14:15:30 2018 -0700 |
tree | 3cb8abaee00929991d6a10a83ba2fdd6065ea219 | |
parent | e5f53c74ab76a0d7b83cf00f2a4622bd0c6884d9 [diff] |
tcti: Use separate structures for the device and mssim TCTI contexts. Using the same structure for both the device and mssim TCTI was lazy. We were also using the same magic number for both modules which had the potential to cause confusion if one library was passed a TCTI initialized by the other. This patch resolves both of these issues by breaking the old TSS2_TCTI_CONTEXT_INTEL structure up into the TSS2_TCTI_COMMON_CONTEXT and a structure specific to the device and mssim TCTIs. To accomplish this we rename the old 'tcti' module to 'tcti-common'. This module defines a context structure containing all of the data common to both the device and mssim TCTIs. This includes the v2 structure as well as a header structure, the enumeration to track the state machine as well as the locality. We also create new header files for the device and mssim TCTI. In these headers we define structures specific to each module that hold the file descriptor for the device TCTI and the socket file descriptors for the mssim TCTI. Another significant change in this commit is the way we're now casting the TCTI context structures passed into the functions for each TCTI module. Functions in the device and mssim modules that are passed the opaque TSS2_TCTI_CONTEXT structure start by first checking the magic number in the context to be sure it's the right one for the module. If this succeeds they then "down-cast" the structure to the TSS2_TCTI_COMMON_CONTEXT and then use this structure to perform all of the state checks. This reduces the number of unsafe cast operations that we have to perform. Finally there are a number of changes in this commit that qualify as cleanup. This includes some name changes for variable and macro names to align with the name changes. Signed-off-by: Philip Tricca <philip.b.tricca@intel.com>
This repository hosts source code implementing the Trusted Computing Group's (TCG) TPM2 Software Stack (TSS). This stack consists of the following layers from top to bottom:
Instructions to build and install tpm2-tss are available in the INSTALL file.
If you're looking to discuss the source code in this project or get some questions answered you should join the 01.org TPM2 mailing list: https://lists.01.org/mailman/listinfo/tpm2. We also have an IRC channel set up on FreeNode called #tpm2.0-tss.
This repository contains a test suite intended to exercise the TCTI, SAPI and ESAPI code. This test suite is not intended to test a TPM implementation, so this test suite should only be run against a TPM simulator. If this test suite is executed against a TPM other than the software simulator it may cause damage to the TPM (NV storage wear out, etc.). You have been warned.
The TPM library specification contains reference code sufficient to construct a software TPM 2.0 simulator. This code was provided by Microsoft and they provide a binary download for Windows here. IBM has repackaged this code with a few Makefiles so that the Microsoft code can be built and run on Linux systems. The Linux version of the Microsoft TPM 2.0 simulator can be obtained here. Once you've downloaded and successfully built and execute the simulator it will, by default, be accepting connections on the localhost, TCP ports 2321 and 2322.
Issues building or running the simulator should be reported to the IBM software TPM2 project.
NOTE: The Intel TCG TSS is currently tested against version 974 of the simulator. Compatibility with later versions has not yet been tested.
To test the various TCTI, SAPI and ESAPI api calls, unit and integration tests can be run by configuring the build to enable unit testing and running the "check" build target. It is recommended to use a simulator for testing, and the simulator will be automatically launched by the tests. Please review the dependency list in INSTALL for dependencies when building the test suite.
$ ./configure --enable-unit --with-simulatorbin=$HOME/ibmtpm/src/tpm_server $ make -j$(nproc) check
This will generate a file called "test-suite.log" in the root of the build directory.
Please report failures in a Github 'issue' with a full log of the test run.
NOTE: The unit and integration tests can be enabled independently. The --enable-unit option controls unit tests, and --with-simulatorbin controls the integration tests.
SAPI library, TAB/RM, and Test Code Block Diagram:
├── doc : various bits of documentation
├── include : header files installed in $(includedir)
│ └── tss2 : all public headers for this project
├── lib : data files used by the build or installed into $(libdir)
├── m4 : autoconf support macros
├── man : man pages
├── script : scripts used by the build or CI
├── src : all source files
│ ├── tss2-esys : enhanced system API (ESAPI) implementation
│ │ └── api : ESAPI TPM API implementation
│ ├── tss2-mu : TPM2 type marshaling/unmarshaling (MU) API implementation
│ ├── tss2-sys : system API (SAPI) implementation
│ │ └── api : SAPI public API implementation
│ ├── tss2-tcti : TCTI implementations for device and mssim
│ └── util : Internal utility library (e.g. logging framework)
└── test : test code
├── integration : integration test harness and test cases
├── tpmclient : monolithic, legacy test application
└── unit : unit tests