-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Improve TPM DUK resealing UX #1653
Comments
@UndeadDevel should this be part of the PR? Can you propose changes? I'm stalled under too many tasks and expected deliverables and I miss time and resources. I would cherry pick your commits. |
@tlaurion Maybe this weekend or next week, but can't promise anything. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
After certain dom0 updates it becomes necessary to reseal the TPM DUK (e.g. new kernel, so boot option list changed). The following secrets must be entered in the following order to make this happen:
AFAICT if any one of those is not entered correctly (not sure about the last one, but this is definitely true for 1-3) then the entire process will fail and has to be started over, which is pretty bad UX as we're talking about a lot of complex secrets.
Describe the solution you'd like
Similarly to what was implemented in #1595, i.e. allow multiple tries, at least for the LUKS DRK, new TPM DUK and User GPG PIN (ideally for TPM Ownership passphrase as well, but that may be problematic regarding rate-limiting by the TPM).
Describe alternatives you've considered
At the very least my suggestion in the other review should be implemented (move the validation of the new TPM DUK passphrase up to occur before the LUKS DRK passphrase entry). But really 1, 2 and 4 in above list should allow multiple tries.
The text was updated successfully, but these errors were encountered: