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

Move prior PCR management into QLDB #2502

Open
evq opened this issue May 8, 2024 · 1 comment
Open

Move prior PCR management into QLDB #2502

evq opened this issue May 8, 2024 · 1 comment
Labels
nitro-payments spec needed a specification is needed before development can begin because this change would not be contained

Comments

@evq
Copy link
Contributor

evq commented May 8, 2024

I propose that to improve usability and reduce the chances of PCR updates being forgotten, we look into migrating the prior PCR list to QLDB. It could for instance be signed by a vault derived key in order to authenticate it's providence as a PCR which we completed bootstrap for.

@Sneagan notes that we could do this at time of first prepare/authorize rather than at bootstrap time.

cc @kdenhartog

@evq evq added nitro-payments spec needed a specification is needed before development can begin because this change would not be contained labels May 8, 2024
@kdenhartog
Copy link
Member

makes sense to me. I like the idea of handling PCR checking at the point of prepare/authorize. It's not necessary if we have certainty around the first, but ideally we could do this during each authorize call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nitro-payments spec needed a specification is needed before development can begin because this change would not be contained
Projects
None yet
Development

No branches or pull requests

2 participants