oxidecomputer / oxidecomputer/sush
Need production key & certificate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 11
Description
The current job-signing key is named UNTRUSTED Support Shell Prototype, living in the sandbox OSS deployment. We need a production key and a certificate for it. Eventually we'd like an intermediate signed by Oxide's offline root, but for now, a self-signed cert for a permslip/KMS hosted key should be sufficient.
This issue must be closed before sush may be merged into Omicron; see oxidecomputer/omicron#11252.
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 reviewing how the current UNTRUSTED Support Shell Prototype job-signing key is represented in the sandbox OSS deployment and how a permslip/KMS-hosted key is handled. Done means a production key and certificate exist, with a self-signed certificate acceptable for now, and the issue is closed before sush is merged into Omicron.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100