-
Notifications
You must be signed in to change notification settings - Fork 45
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
Handle TPM2 + passphrase #198
Comments
Counterpart implementation of systemd/systemd#22563 Implements #198
I added booster boilerplate to handle PIN. Now I need to use the pincode to unseal the value. I am looking for help from someone who understands the |
Counterpart implementation of systemd/systemd#22563 Implements #198
Alright, I think I figured out the logic. I improved booster code and the test shows it is able to unlock a drive locked with systems tpm+pin. Please pull the changes from |
Thanks for looking into this. Interestingly the log complains about no tpm devices being found just before obtaining password for the tpm2 token |
Booster tries to unlock all possible LUKS slots in parallel. Such an algorithm would work well if slots are non-interactive (non-PIN tpm, clevis, ...). The first valid slot unlocks the partition, and other slots processors get canceled. In your case, you have 2 interactive slots that require some sort of pin/password. So the prompts you see are interleaved. My guess you expected to see only 1 interactive slot processed at a time. But which one should be processed/prompted first? And why? |
A TPM2 PIN is supposed to be safe, yet convenient (lowish entropy; easy to type). If a user went to trouble of enrolling it, it's probably the preferable way of unlocking. |
Counterpart implementation of systemd/systemd#22563 Implements #198
Counterpart implementation of systemd/systemd#22563 Implements #198
Counterpart implementation of systemd/systemd#22563 Implements #198
A while ago systemd got support for TPM2 + passphrase setup:
systemd/systemd#22563
It would be nice if booster supported unlocking such volumes as well
The text was updated successfully, but these errors were encountered: