oxidecomputer / oxidecomputer/dice-util
PlatformId from CSR
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 3
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 16
Description
For PkiPaths we provide a TryFrom in the PlatformId type to walk the PkiPath and extract the PlatformId string. The dice-mfg command does the same thing for CSRs as a way to ensure that the platform being manufactured generated a CSR with a subject field in the expected form & with the expected content (https://github.com/oxidecomputer/dice-util/blob/10952e8d9599b735b85d480af3560a11700e5b64/dice-mfg/src/lib.rs#L107). For the sake of consistency we should provide a TryFrom<CertReq> impl.
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 in dice-mfg/src/lib.rs around the CSR handling referenced near line 107, and compare it with the existing PlatformId TryFrom implementation. Add the corresponding TryFrom behavior so it extracts and validates the subject in the expected form, matching the manufacturing command; done means the conversion is available for CSRs and preserves that validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100