-
Notifications
You must be signed in to change notification settings - Fork 43
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
Calculate measurements outside of TDX #263
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/PEK-1442.
|
the RTMR[0-2] measurement values are calculated from eventlog entries digest, you can display the eventlog with the tool we have here : https://github.com/canonical/tdx/tree/noble-24.04/tests/lib/tdx-tools the command is : |
I think this is not what user want here. These eventlogs or the tool Also I think the eventlogs or the tool doesn't calculate the measurements but just read from the already generated reports, specifically at |
Good question, AFAIU, part of the measurements cover the real hardware so I don't think we can generate the all reference values off-board, potentially, some part of the RTMRs can be computed off-board but for now, this topic is a quite complex challenge and we are not yet working on it |
Thank you for all this wonderful information. Its a great start! The scenario I am trying to solve for is:
From what you described, It sounds like this cannot be done with the TDX attestation alone and would require looking at the TDX Event log (This would allow you to accept the hardware values you cannot verify (provided by the HOST's hardware) and verify the value provided by the GUEST) My understanding is there are 4 ingredients that we must verify to boot a machine (i included the sha384 of each)
After dumping the logs using your tools i Found the hash for initrd only I attached the event log Any suggestions? |
@YurkoWasHere this probably needs some tweaking for your use-case, but check out our internal tool we use in Contrast to do TDX measurement precalulation: https://github.com/edgelesssys/contrast/blob/main/tools/tdx-measure/main.go The diff between your calculated parameters is probably caused by not the raw components (e.g. kernel ELF) being measured, but their in-memory forms. Check out #298 for more on that. |
After a TDX Quote has been generated, attested to and signed it contains measurements (RTMR 0-4)
Given the access to the boot component (ovmf, kernel, kernel parameters and initrd) how can some one calculate the RTMRs values outside of the TDX environment to validate the quote is as expected.
The text was updated successfully, but these errors were encountered: