oxidecomputer / oxidecomputer/dice-util
attestation retries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 3
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 16
Description
If verification of the signature over the attestation (log & nonce) fails it could be that a measurement was recorded between the time we got the log and the attestation. This is a race condition inherent to the protocol since we get the log and the attestation in two separate messages. There are couple of different things we can do In this case:
- get the log again and retry verification, if the second attempt fails return an error
- signal to the caller that they should try again
The first option seems the most reasonable. The second may cause confusion as it punts the decision to the caller.
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 locating the attestation signature-verification entry point and the code that retrieves the log and nonce. Reproduce the race described in the issue, then make verification retry after fetching the log again and return an error when the second attempt fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100