oxidecomputer / oxidecomputer/omicron
Extract RKTH from CMPA RotPage in inventory to use in planner
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
To make RoT and RoT bootloader artifact verification in the planner more robust, we'd like to compare an RoT/RoT bootloader's sign field in the caboose (which is the RKTH) to the CMPA's rkth field found in inventory.
Today all we get from inventory for RotPage are base64 encoded blobs. We need to have a way to safely decode and extract this information so the planner can use it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace how inventory exposes RotPage blobs and how the planner currently verifies RoT and RoT bootloader artifacts, using the linked discussion as context. The work is done when the CMPA rkth value can be safely decoded from inventory and compared with the caboose sign field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100