Need production key & certificate

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
infrastructure, security

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.

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.

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.