Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / ms-tpm-20-ref / 2c1fa6f0ace16e9d8d40f5f929c7bbf56de13e92
commit2c1fa6f0ace16e9d8d40f5f929c7bbf56de13e92[log] [tgz]
authorJonas Witschel <diabonas@gmx.de>Thu Nov 07 00:30:24 2019 +0000
committerAndrey Marochko <Andrey.Marochko@microsoft.com>Wed Nov 06 16:30:24 2019 -0800
treea0127d6bd94950b76928cdf95e2f02d0deb9bd08
parent39e7306e235a6b2e09e454af08de285388e7a4b4 [diff]
Use appropriate error for incorrect reserved bits in TPMA structures (#39)

According to the TPM 2.0 Library specification, Part 2 (rev. 1.38),
Table 2, a TPM_RC_RESERVED_BITS error shall be used if "a non-zero value
was found in a reserved field of an attribute structure (TPMA_)". This
is done correctly when compiling with TABLE_DRIVEN_MARSHAL=NO, cf.
Marshal.c, but for TABLE_DRIVEN_MARSHAL=YES the incorrect error
TPM_RC_ATTRIBUTES is used instead.

Fixes: f76525015bd33fb83933f958d712cf975a5e30ae
1 file changed
tree: a0127d6bd94950b76928cdf95e2f02d0deb9bd08
  1. external/
  2. Samples/
  3. TPMCmd/
  4. .gitignore
  5. .gitmodules
  6. .travis.yml
  7. CONTRIBUTING.md
  8. CppProperties.json
  9. LICENSE
  10. README.md
README.md

MS TPM 2.0 Reference Implementation

Build Status

This is the official TCG reference implementation of the TPM 2.0 Specification. The project contains complete source code of the reference implementation with a Microsoft Visual Studio solution and Linux autotools build scripts.

See the definition of the SPEC_VERSION, SPEC_YEAR and SPEC_DAY_OF_YEAR values in the TpmTypes.h header for the exact revision/date of the TPM 2.0 specification, which the given source tree snapshot corresponds to.

Visual Studio build

Before building the Visual Studio solution:

  1. Uncomment and update the definitions of the following macros in the VendorString.h header:
  • MANUFACTURER
  • VENDOR_STRING_1
  • FIRMWARE_V1 and FIRMWARE_V2
  1. Setup the underlying cryptographic library:

OpenSSL library

  1. Create TPMCmd/lib folder and place a static OpenSSL library (libeay32.lib or libcrypto.lib) there. This may be either complete static library, or import library accompanying the corresponding DLL. In the latter case you'll need to copy the OpenSSL DLL into the standard Windows search path, so that it is available when you run the simulator executable (e.g. copy it into the same folder where simulator.exe is located).

    If you use libcrypto.lib, you'll need to either update Linker|Input|Additional Dependencies property of the Tpm project in the simulator solution or, alternatively, rename libcrypto.lib to libeay32.lib.

    Recommended version of OpenSSL is 1.0.2d or higher.

  2. Create TPMCmd/OsslInclude/openssl folder and copy there the contents of the openssl/include/openssl folder of the OpenSSL source tree used to build the static library used on the step 2).

  3. Build the solution with either Debug or Release as the active configuration.

Wolfcrypt library (wolfSSL)

  1. WolfSSL is included as a submodule. Initialize and update the submodule to fetch the project and checkout the appropriate commit.

     > git submodule init
 > git submodule update

    The current commit will point the minimum recommended version of wolfSSL. Moving to a more recent tag or commit should also be supported but might not be tested.

  2. Build the solution with either WolfDebug or WolfRelease as the active configuration, either from inside the Visual Studio or with the following command line:

     > msbuild TPMCmd\simulator.sln /p:Configuration=WolfDebug

Linux build

Follows the common ./bootstrap && ./configure && make convention.

Note that autotools scripts require the following prerequisite packages: autoconf-archive, pkg-config. Their absence is not automatically detected. The build also requires libssl-dev package to be installed.