-
Notifications
You must be signed in to change notification settings - Fork 82
Separate FMC Cert/CSR Owner and Vendor Info #2837
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
base: main
Are you sure you want to change the base?
Separate FMC Cert/CSR Owner and Vendor Info #2837
Conversation
nquarton
commented
Nov 24, 2025
- Separate owner and vendor fuse info
- Make TCB type names more specific in FMC cert/CSR and RT cert
- Add missing testing for FMC MLDSA CSR
|
It was brought to my attention that several related changes are needed in the PCR generation which feeds key derivation for the FMC Alias layer. Those changes will be made and added here ASAP. |
58fac4e to
22c7dcb
Compare
This is included in this PR now. Ideally, there would be shared code to keep the key derivation and TCB infos in-line, but the formatting and grouping for the two are completely different (one is TCB info and one goes into the PCR and PCR log) so there really isn't much of an opportunity to consolidate this. |
22c7dcb to
30e5e6d
Compare
|
PR to update spec with these changes is here: chipsalliance/Caliptra#579 |
|
Note a change in direction was made here where I need to add the vendor PK index used and SVN from the manifest back into the cert and FMC key derivation. |
30e5e6d to
4211de4
Compare
4211de4 to
b8f53e3
Compare
These have been re-added as well as the bool indicator for the owner pub key being fused. This is ready for review again. |
| data_vault: &DataVault, | ||
| sha2_512_384: &mut Sha2_512_384, | ||
| ) -> CaliptraResult<[u8; 48]> { | ||
| // NOTE: The contents of this TCB info and FMC PCR info must stay in sync. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to have a common struct with all of the information needed for both? You could add helper functions for both scenarios something like tcb_info() and pcr_info(). That could help make sure it isn't forgotten in one place or the other
b8f53e3 to
b8526c8
Compare
- Separate owner and vendor fuse info - Add more contents to TCB owner/vendor TCB info - Align FMC TCI with TCB info contents - Make TCB type names more specific in FMC cert/CSR and RT cert - Add missing testing for FMC MLDSA CSR
b8526c8 to
973dd02
Compare
- SVN - pub key index (ecc and pqc) - owner pub key hash in fuses (bool indicator)
973dd02 to
23eb769
Compare