oxidecomputer / oxidecomputer/sush
Job-signing certificate revocation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 11
Description
We should be able to revoke any (root or leaf) job-signing certificate. The revocation list should be persisted to the M.2 drives, loaded at boot, and distributed via the gossip protocol. On receipt of a new revocation, servers should stop all jobs signed with the revoked certificate.
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 job-signing certificate verification and job execution paths, then trace boot-time state loading and gossip message handling. Determine how revocations can be persisted on M.2 drives and propagated between servers. Done means root and leaf certificates can be revoked, the list survives reboot, new revocations spread through gossip, and affected jobs stop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100