-
Notifications
You must be signed in to change notification settings - Fork 3
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
Include tpm2 support in the image #369
Comments
This would be a great feature indeed, but I believe you still would have to rebuild the initramfs at least once after you changed your |
It appears that on Silverblue 38 (as of 2023-06-17), the following packages are installed on the base rpm-ostree: I was able to enroll my via Regenerating initramfs is still needed but the packages are available now. |
We should figure out why those modules are not enabled by default in our initramfs:
Other instances of this: |
Thanks for the report. This issue is now tracked in https://gitlab.com/fedora/ostree/sig/-/issues/33 thus I'll close this one. |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
In order to use
systemd-cryptenroll
against a tpm2 module on Fedora Silverblue (as of 36), a user must layertpm2-tools
and run this command:rpm-ostree initramfs --enable --arg=--force-add --arg=tpm2-tss
before doing the enrollmentDescribe the solution you'd like
A clear and concise description of what you want to happen.
If tpm2-tools was included in the rpm-ostree image and support for tpm2-tss was included by default in the initramfs, a user could jump straight to the
systemd-cryptenroll
step. Fedora could even offer to enable it during the install process.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
We could continue doing the above manually- I'm also raising this issue to document the required steps.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: