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

TPM provider should establish most-secure primitives for itself #121

Closed
ionut-arm opened this issue Mar 5, 2020 · 0 comments · Fixed by #168
Closed

TPM provider should establish most-secure primitives for itself #121

ionut-arm opened this issue Mar 5, 2020 · 0 comments · Fixed by #168
Labels
enhancement New feature or request

Comments

@ionut-arm
Copy link
Member

Following the RaspberryPi tests, it's quite apparent that not all TPMs support the primitives that we'd want to use by default in, for example, securing our authentication sessions.

Based on work to be done in parallaxsecond/rust-tss-esapi#38 we can pre-select a list of primitives and their parameters, and find the most desirable one that's supported, at runtime.

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

Successfully merging a pull request may close this issue.

1 participant