oxidecomputer / oxidecomputer/dice-util
yubihsm attestation analysis
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 3
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 16
Description
The YubiHSM provides us with a nice mechanism (attestation) as a way for us to evaluate a claim by the YubiHSM, namely that a key was created on that YubiHSM and that it has a particular set of properties. We collect this data in oks but we do not yet have a mechanism to analyze them to ensure they are trustworthy (PKI path validation).
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 examining how YubiHSM attestation data is collected in oks. Then identify the PKI path-validation requirements needed to establish that the attestation is trustworthy; the work is complete when collected attestations can be analyzed against those requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100