commit | e394cffe3add7874299b9571e0b5140b4dc51dfe | [log] [tgz] |
---|---|---|
author | Philip Tricca <philip.b.tricca@intel.com> | Wed Apr 18 08:36:06 2018 -0700 |
committer | Philip Tricca <philip.b.tricca@intel.com> | Tue Apr 24 12:01:51 2018 -0700 |
tree | 0f35dcf5eb80d05a519aedb2544126f27a41f71c | |
parent | f517ee5a1afe58d30662167fb7fca55366c8137d [diff] |
tcti-mssim: Replace liburiparser with custom key/value pair parser. This removes our use of liburiparser with a custom key / value pair parser. The parser is implemented in the key-value-parse module under the util directory. The parser is designed to extract a series of key / value pairs where each key and value are separated by the '=' character and each pair is separated by the ',' character. The parser is composed of three parts: 1) The 'parse_key_value' function is used to extract key /value pairs separated by the '=' character. This function modifies the string by using the 'strok_r' function to extract the key and value. A reference to each is then returned to the caller using the key_value_t structure. 2) The 'parse_key_value_string' function is used to extract each key / value pair parsing the provided string on the ',' character using the same method as the 'parse_key_value' function. Each string containing a key / value pair is then passed to the 'parse_key_value' function to extract the individual components. 3) Finally the 'parse_key_value_string' function is passed a function pointer conforming to the 'KeyValueFunc' type. This function is invoked for each key / value pair extracted and is passed a reference to the key_value_t structure from the previous step. It is also passed a void pointer to some caller provided data structure which allows the callback to do something with the key / value pairs. For the purposes of the mssim TCTI we simply identify valid / invalid keys and store their values in a data structure. Once the parser is done extracting data from the provided string the mssim TCTI will either return an error indicating the configuration string was invalid, or continue initializing the TCTI based on the provided data. If a NULL configuration string is provided defaults are used. Additionally this commit: 1) Removes the check for liburiparser from the autoconf file. 2) Updates the .travis.yml file to no longer install liburiparser as a build dependency. 3) Adds unit tests for the functions described above. 4) Updates existing tests and test infrastructure to use configuration strings in the new format. 5) Updates the man page for the Tss2_Tcti_Mssim_Init fucntion to describe the new configuration string format. 6) Updates the default configuration string to use 'localhost' instead of a raw IPv4 address to make the library friendly to platforms that only support IPv6. 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