theupdateframework / theupdateframework/rust-tuf
Metadata update needs better Ok/Err logic
Open
Nobody has claimed this yet.
Feature :: Improvement
Priority :: Medium
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
Currently the outcomes of updating are:
- Things are ok, we did an update.
- Things are ok, we did not update.
- Everything is borked and on fire.
Return should be:
- Update happened, we are in a legal state.
- Update did not happen, we are in a legal state.
- We are in an illegal state.
For example, it may be reasonable for this to happen:
- Update local root to v1
- Update local timestamp to v1
- Update local snapshot to v1
- Update local targets to v1
Then
- Try to update remote timestamp to v2, but fail
- Continue anyway because the TUF internal state is consistent
Contributor guide
No contributing guide indexed for this repository
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 metadata update flow and its current Ok/Err return behavior. Compare it with the issue's local-update and failed-remote-update sequence, then define and test distinct outcomes for a successful update, a skipped update in a legal state, and an illegal internal state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100