forked from microsoft/ms-tpm-20-ref
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implements platform hooks to enable wolfcrypt as an alternative crypto engine. ECC, RSA, AES, and hashing is enabled and tested. Adds specific wolfSSL configurations to the TPM simulator project.
- Loading branch information
Showing
23 changed files
with
1,719 additions
and
518 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,22 +1,44 @@ | ||
| # 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: | ||
| ## 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 | ||
|
|
||
| 2) 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. | ||
| 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 | ||
|
|
||
| 2. 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. | ||
| 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). | ||
|
|
||
| 2. 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. | ||
|
|
||
| 3) 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). | ||
| 2. Build the solution with either WolfDebug or WolfRelease as the active configuration. | ||
|
|
||
| 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). | ||
| > msbuild TPMCmd\simulator.sln /p:Configuration=WolfDebug |
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.