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

Add support for self-signed FMC_Alias CSR #1837

Closed
fdamato opened this issue Dec 4, 2024 · 1 comment · Fixed by #1863
Closed

Add support for self-signed FMC_Alias CSR #1837

fdamato opened this issue Dec 4, 2024 · 1 comment · Fixed by #1863
Assignees

Comments

@fdamato
Copy link
Contributor

fdamato commented Dec 4, 2024

To facilitate Owner Identity Transfer, it's necessary for the Caliptra Runtime Firmware to offer an API that yields a self-signed CSR, ideally of the IDEVID. This would enable the Owner PKI to endorse the complete Device Certificate Chain using their own Certificate Authority.

At present, Caliptra 1.2 ROM only produces a self-signed IDEVID CSR when the "mfg_flag_gen_idev_id_csr" is activated.
The aim of this request is to extend CSR support to Caliptra 1.1 ROM integrators.

There are two potential methods to achieve this.

Option 1:
- At cold boot, Caliptra FMC should consistently generate an FMC_ALIAS CSR, self-sign it, and save it in persistent memory.
- Caliptra Runtime Firmware should introduce a new API to access the FMC_ALIAS CSR signed by the FMC.

Option 2:
- At cold boot, Caliptra FMC should consistently generate an FMC_ALIAS CSR, self-sign it, and store its signature in persistent memory.
- Caliptra Runtime Firmware should introduce a new API to rebuild the FMC_ALIAS CSR (utilizing its signature created by the FMC and saved in persistent memory).

While Option 2 might add a slight increase in complexity to the Runtime Firmware, it could potentially save a few bytes in persistent memory.

@nquarton nquarton linked a pull request Jan 30, 2025 that will close this issue
@nquarton
Copy link
Contributor

Completed in #1863

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

Successfully merging a pull request may close this issue.

3 participants