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

Decide and implement a new serialization format for KeyInfo #509

Closed
Tracked by #486
MattDavis00 opened this issue Aug 31, 2021 · 0 comments
Closed
Tracked by #486

Decide and implement a new serialization format for KeyInfo #509

MattDavis00 opened this issue Aug 31, 2021 · 0 comments
Labels
bug Something isn't working help wanted Extra attention is needed platforms Compatibility with different secure services or hardware platforms security Issues related to the security and privacy of the service stability Issues related to the stability of the service

Comments

@MattDavis00
Copy link
Member

As described in #504, specifically here; the way we serialize KeyInfo will have to change due to the TPM issue.
This issue will track the progress of a design decision & implementation for the new KeyInfo serialization strategy (required for both #504 and #486 progress)

@MattDavis00 MattDavis00 added bug Something isn't working help wanted Extra attention is needed security Issues related to the security and privacy of the service platforms Compatibility with different secure services or hardware platforms stability Issues related to the stability of the service labels Aug 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed platforms Compatibility with different secure services or hardware platforms security Issues related to the security and privacy of the service stability Issues related to the stability of the service
Projects
None yet
Development

No branches or pull requests

1 participant