theupdateframework / theupdateframework/specification
Repository workflows: document how a repository recovers from compromise
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
This may be in secondary literature #91 or it may belong as part of the specification, but either way, we should capture more guidance for repository operators (and repository tooling implementers).
Specifically for this issue, what should a repository do to recover from compromise?
For fast forward attacks, the Mercury paper makes some suggestions in section 5.3 and there's some more thoughts in https://github.com/theupdateframework/specification/pull/150/files#r710834950 and #150 more generally.
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 reading section 5.3 of the Mercury paper, the discussion in #91, and review comment r710834950 plus pull request #150. Determine whether recovery guidance belongs in the specification or secondary literature, then document an agreed approach for repository operators and tooling implementers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100