-
Notifications
You must be signed in to change notification settings - Fork 71
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
Allow loading of cached keys #313
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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.
Could you add tests for LoadCachedKey, e.g., loading successfully and failing the load with a bad handle?
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.
Please fix the linter issues
New Features: [launcher] Add capability to open ports google#294 Allow loading of cached keys google#313 Other Changes: Use legacy tpm2 at its new path google#318 Add GoReleaser release action for gotpm CLI google#319 Update go-tpm dependency to 0.9.0 google#321
Implementation for #237.
As discussed in the issue, I exposed the different sessions to be able to set it in the loaded key.
If you don't want to expose all possible sessions, exposing just the
NullSession
is sufficient for our use-case.