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

Both RT Journey Measurements Are Equal Following a FW Update #1673

Open
nquarton opened this issue Sep 14, 2024 · 1 comment
Open

Both RT Journey Measurements Are Equal Following a FW Update #1673

nquarton opened this issue Sep 14, 2024 · 1 comment

Comments

@nquarton
Copy link
Contributor

Both RTJM values are the same values following a FW update. This seems unexpected given the way we understand they are calculated and the fact they differ in the cold boot case.

While we understand one of these values is not useful as it is a journey of a journey measurement, the concern is that something may be broken because they are equal.

image

@jhand2
Copy link
Collaborator

jhand2 commented Sep 25, 2024

This is intentional, but I'm open to representing it a different way if we prefer. During hitless update, we populate the RTJM with the latest value of the RT journey PCR: https://github.com/chipsalliance/caliptra-sw/blob/main/runtime/src/drivers.rs. See update_dpe_rt_journey implementation.

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

No branches or pull requests

2 participants