-
Notifications
You must be signed in to change notification settings - Fork 1
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
Adapt GRUB code for the TrenchBoot boot protocol #31
Comments
Latest changes can be seen at TrenchBoot/grub@b53ec06...tb-2.12-57-linux-amd. There is only one new commit for AMD SKINIT (TrenchBoot/grub@fc42d91), one new commit with a fix (TrenchBoot/grub@cc5e2c0), the rest of the new changes were integrated into previously existing commits. When updated GRUB is used along with SKL built from TrenchBoot/secure-kernel-loader#21 on APU3 with Seabios, the following output is produced on slaunch: Details
|
Log after enabling IOMMU on the same platform:
However, I think that the changes cover also #32 and #33. For the latter, we can update Qubes OS builder CI (the config we used was recently removed), but #32 will be complete together with this issue. I've added two comments that should be fixed: TrenchBoot/grub@fc42d91#r145084754 (suboptimal memory allocation) and TrenchBoot/grub@da0161f#r145085228 (timing problem that caused unexpected PCR values on release builds earlier). |
Addressed the comments, changes: https://github.com/TrenchBoot/grub/compare/fc42d91bfeb1cb412bbaa5e846d6685a234d42ea..tb-2.12-57-linux-amd (also spotted and fixed some incorrect formatting). |
For easier tracking and review, changes to GRUB were moved to TrenchBoot/grub#22. That PR has been merged, which closes this task and #32. |
Refreshing existing GRUB code and implementing necessary fixes for the most up-to-date TrenchBoot boot protocol. This also includes changes to code style to make it compatible with GRUB's expectations. The code will be pushed to the TrenchBoot GRUB repository to serve as a foundation for future TrenchBoot activities.
The text was updated successfully, but these errors were encountered: