-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Microsoft Reference Implementation for the Simulator #20
Conversation
What architecture? Why can't we build this from source rather than having precompiled blobs? |
Also, how will this affect consumers of go-tpm-tools/simulator? It is already used extensively in integration tests for go-attestation and I has a citc with WIP tests for go-tpm. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If keeping the .a files is absolutely essential, would you consider keeping both simulators as part of the repo, with different import paths (but hopefully identical/similar APIs?)
I managed to get everything working normally. Also note that the remote is currently my fork (see the upstream PRs in the description). @twitchy-jsonp PTAL. Due to the large git diff, it might be easier to look at each commit individually. We should also make sure to keep the git history when merging this CL. |
Wheres
|
As the C code is in a submodule, you have to use |
LGTM.
|
The change:
simulator.c
which textually includes all the.c
files to get around the terrible CGO build system.This gives us:
Edit: Note that the remote is actually my fork. To make everything clean, I had to start addressing microsoft/ms-tpm-20-ref#33 with the following PRs: