theupdateframework / theupdateframework/taps
Discussion of TAP 12: Improving keyid flexibility
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 37
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
This is a thread to discuss TAP 12, introduced in #112.
The corresponding issue for the reference implementation is theupdateframework/tuf#1084.
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 TAP 12 and the issue that introduced it, #112, then review the corresponding reference-implementation discussion in theupdateframework/tuf#1084. Done would require an agreed direction for improving keyid flexibility, but this issue records discussion rather than a defined implementation task.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100