Google Git
Sign in
android / platform / external / ms-tpm-20-ref / 2140b75
commit2140b7523faf89ccb0503fb40ca339855347e2f3[log] [tgz]
authorPhilip Tricca <philip.b.tricca@intel.com>Wed Jun 06 11:01:51 2018 -0700
committerPhilip Tricca <philip.b.tricca@intel.com>Sun Dec 09 19:12:37 2018 -0800
tree4a0b1a46ac3909139b22d1e3dab77e611c6217c3
parent65b65354c6cce3212d9c512ec3ae2e23fe37c94d [diff]
tpm: Use compiler environment to determine proper RADIX_BITS.

Expecting users to change code in order to build for 64bit environments
isn't very user friendly. In the case of the RADIX_BITS we can make this
easier on users (and automated builds) by using the compiler environment
to do the detection for us. Currently the implementation is limited to
the __x86_64__ / __i386__ and _WIN64 / _WIN32 macros from linux /
windows compilers respectively.

An alternative implementation may have used the OpenSSL bn_ops values to
determine 32 vs 64bit. This ends up being awkward since Implementation.h
is included by other modules and they then end up depending on the
openssl headers.

Signed-off-by: Philip Tricca <philip.b.tricca@intel.com>
1 file changed
tree: 4a0b1a46ac3909139b22d1e3dab77e611c6217c3
  1. external/
  2. Samples/
  3. TPMCmd/
  4. .gitignore
  5. .gitmodules
  6. CONTRIBUTING.md
  7. LICENSE
  8. README.md
README.md

MS TPM 2.0 Reference Implementation

This is a Microsoft Visual Studio solution that contains reference implementation of the TPM 2.0 Specification by TCG available at https://trustedcomputinggroup.org/tpm-library-specification.

See the TPMCmd/tpm/include/TpmTypes.h header for the exact revision/date of the TPM 2.0 specification issue, which the given source tree snapshot corresponds to.

Before building the solution

  1. Uncomment and update the definitions of the following macros in the TPMCmd/tpm/include/VendorString.h header:
  • MANUFACTURER
  • VENDOR_STRING_1
  • FIRMWARE_V1 and FIRMWARE_V2
  1. Setup the cryptography platform the TPM will use for the underlying primitives:

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 was 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).

    If you use OpenSSL 1.1, you'll additionally need to:

  • Copy the openssl/crypto/bn/bn_lcl.h header to the TPMCmd/OsslInclude/openssl folder;
  • Create TPMCmd/OsslInclude/openssl/internal folder and copy there the contents of the openssl/crypto/include/internal folder (do not confuse it with the openssl/include/internal folder that need not be copied).
  1. 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