Skip to content
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

Moving read_nvram(...) into XTT library #78

Closed
kathrynfejer opened this issue Oct 31, 2018 · 2 comments
Closed

Moving read_nvram(...) into XTT library #78

kathrynfejer opened this issue Oct 31, 2018 · 2 comments

Comments

@kathrynfejer
Copy link
Contributor

kathrynfejer commented Oct 31, 2018

While implementing support of XTT for enftun, we realized that read_nvram and other functions may be able to move into the xtt library.

read_nvram currently creates a TCTI context each time it reads from the TPM. Is it possible that we could create a function to do that once, and then use that context/credentials to read out the information?

@drbild
Copy link
Contributor

drbild commented Nov 2, 2018

@kathrynfejer Could you split this into three separate issues, one for read_nvram, one for defining the "context" formats, and one for making the group_context stuff more object-oriented.

That will be easier for discussions. It's fine to reference one from the other.

@zanebeckwith
Copy link
Collaborator

This can now be implemented by moving the nvram.[h,c] code from xaptum-tpm into this project.

That should live in the xaptum/tpm namespace, and use the handles defined in xaptum/tpm/handles.h. The client code should then be refactored to create a TPM system context once, and pass it to the xtt_tpm_read_object (previouslyxtpm_read_object) function for each NVRAM "object" it needs to read out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants