oxidecomputer / oxidecomputer/dice-util
use type system to enforce correct use of verifier API
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 3
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 16
Description
Parts of this API should only be used after another part of the API. The prime (only?) example is the verify_attestation & verify_measurements functions. These should only be used after the attestation signer cert chain is verified. We can use the type system to do this w/ a few newtypes around the x509_cert::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 reading the verify_attestation and verify_measurements functions and the x509_cert::Certificate usage they rely on. Determine how the attestation signer certificate chain is represented and define what “done” means: the type system should prevent these verification functions from being used before that chain has been verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100