oxidecomputer / oxidecomputer/tufaceous
add test for key rotation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
In a normal, long-lived TUF PKI, 1.root.json expires and a new 2.root.json is generated that is self-signed and signed by keys in 1.root.json. To allow for upgrading into the new root, 1.root.json is also shipped with the repo.
Write a test with this scenario to ensure we can ship a repository with both a 1.root.json and 2.root.json.
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 locating the existing Rust tests and repository-generation entry points for TUF root metadata. Reproduce the scenario with both 1.root.json and 2.root.json, including the self-signature and prior-root signatures, and verify that the repository can be shipped and upgraded with both roots present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100