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

Support BIOS SINIT modules #1470

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Support BIOS SINIT modules #1470

wants to merge 2 commits into from

Conversation

jandryuk
Copy link
Contributor

Intel doesn't really post SINIT modules anymore. Also, with Converged BootGuard and TXT (CBnT), the BIOS-provided ACM doesn't double duty for both BootGuard and TXT. It's something like there can be only a single BIOS ACM. Since it has to be there for BootGuard, it also does TXT.

Since there may not be an SINIT ACM on on disk to match against, we can't rely on it to parse the ACM caps. Instead (kinda ugly) grep it out of txt-stat output. It's logged there by tboot and we just need a single 32bit value.

pcr-calc is updated to accept ACM caps on the command line.

pcr-calc currently uses an ACM file to read out the SINIT capabilities
to determine its calculations.  Add an option to just directly provide
the SINIT capabilities.  This is useful for the case of a BIOS provided
ACM when a file is unavailable.  Otherwise pcr-calc will be unable to
run and you cannot forward seal.

Signed-off-by: Jason Andryuk <[email protected]>
You can have a machine do a measured launch from a BIOS-provided ACM
when you don't have an SINIT ACM file.  In that case, you cannot forward
seal because ml-functions fails when it cannot find a file.

Add a fallback mode for when a file cannot be found to parse the SINIT
capabilities out of the txt-stat output.  It's not pretty, but it may do
the trick.  Then you can use the new -C option to pcr-calc for the
forward seal.

Signed-off-by: Jason Andryuk <[email protected]>
@crogers1 crogers1 self-requested a review May 11, 2023 21:07
@dpsmith
Copy link
Member

dpsmith commented May 12, 2023

Unfortunately this is not ideal, but until a method is crafted to allow dom0 either access (direct memory) or details (expand tboot hypercall), this is probably the best way in the short term.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants