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.

Sign up for GitHub

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

Jump to bottom

Consider using SHA2-256 for RoT FWID measurements #1548

Closed
lzrd opened this issue Oct 6, 2023 · 2 comments
Closed

Consider using SHA2-256 for RoT FWID measurements #1548

lzrd opened this issue Oct 6, 2023 · 2 comments

Comments

@lzrd
Copy link
Contributor

lzrd commented Oct 6, 2023

The software implementation of SHA3-256 adds to flash and RAM requirements more than using the hardware implementation of SHA2-256 that is available from the LPC55 ROM.

TODO:

  • Measure the difference in the resulting Hubris image sizes and decide if the savings are important.
  • Discuss any security implications and decide if they are important for this application.
@lzrd
Copy link
Contributor Author

lzrd commented Oct 6, 2023

I'd like to save some flash and RAM and I don't think that the differences in algorithm strength apply to this case given that there is also a signature check and image format tests.

@lzrd
Copy link
Contributor Author

lzrd commented Mar 21, 2024

Closing, we're all tooled up for SHA3-256 for Firmware ID (FWID) and there doesn't seem to be a compelling reason to move to the HW-supported SHA2-256. Upcoming PR does make the FWID an enum with one SHA3-256 variant to make it easier to change this in the future.

@lzrd lzrd mentioned this issue Mar 21, 2024
Merged
lzrd added a commit that referenced this issue Apr 30, 2024
@lzrd
Update RoT bootloader, a.k.a. stage0 (#1675)
0c001d4 
This PR has four commits to simplify reviewing.

- The first is Laura's macro to manipulate the HASHCRYPT interrupt
vector.
- 2nd is pre-main kernel changes to create a staging area for Bootleby
update and to validate the (now) four RoT flash banks and record those
results for use by update_server.
- 3rd are the API changes to support stage0 update including treating
the bootloader as a separate component with A (active) and B
(stage0next) banks.
  - last is the code in the RoT update_server to actually update stage0

Before merging this PR, Cargo.toml needs to be edited to reference the
gateway-message-service main branch.
Merging needs to be coordinated with an MGS merge.

Closes #1043, #1404, #1548, #1353,
@lzrd lzrd closed this as completed May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lzrd