oxidecomputer / oxidecomputer/omicron
Planner should handle SP/RoT/RoT bootloader rollback protection
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
As per RFD349, the SP/RoT/RoT bootloader will use an epoch based system for rollback protection.
This means that once the EPOC field is populated, the planner should make use of it to verify that the EPOC in the artifact's caboose is larger than the one reported by the inventory's caboose.
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
Start by reading RFD349's rollback-protection section, then locate the planner code that compares artifact and inventory caboose data. Trace how the EPOC field is represented and validated, and identify existing planner tests. Done means the planner enforces the epoch ordering once EPOC is populated and preserves current behavior when it is not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100