theupdateframework / theupdateframework/specification
Add section to TUF specification that covers key revocation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
The TUF specification outlines the Root role and key revocations here.
We should add a separate section that more thoroughly covers key revocation of top-level roles, and how clients are expected to update metadata following these key revocations.
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 with the Root role and key-revocation section linked from docs/tuf-spec.txt, then review the surrounding TUF specification to understand the existing scope. Add a separate section covering revocation of top-level role keys and how clients update metadata afterward; the work is done when both topics are specified clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100