Job-signing certificate revocation

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
distributed-systems, security

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.

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.

Dominant language
Rust
Stars
3
Forks
0
Avg merge
9d 12h
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oxidecomputer/sush

All issues in oxidecomputer/sush

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.