[rom_ext] Audit boot_svc for boot loops
Open
Nobody has claimed this yet.
SW:ROM_EXT
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
Examine flows through the boot_svc code for boot-loop situations.
Example: if one prepares a boot_svc message with a valid `identifier` and an invalid `digest` field, boot_svc will return an error, shutdown, reboot and re-evaluate the still invalid message.
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 tracing the boot_svc flows involved when a message has a valid identifier and invalid digest. Determine where the error, shutdown, reboot, and message re-evaluation occur; done means invalid input no longer causes an unintended boot loop, with regression coverage for this scenario.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100