oxidecomputer / oxidecomputer/propolis
standalone: want ability to run attestation server backed by real or mock RoT
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
Incremental work for #1067
This PR will cover running a VM attestation server via propolis-standalone. Via the standalone configuration TOML file, a standalone user can specify whether to use a real root of trust (via the "IPCC" backend, available on oxide hardware only) or use mock data generated by the vm-attest-proto crate.
The qualifying data for the instance will also be specified in the TOML file.
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 with the linked pull request #1076 and the propolis-standalone entry point. Review how the standalone TOML configuration represents the IPCC and mock vm-attest-proto root-of-trust choices and instance qualifying data. Done means the attestation server can run with either backend as specified in the configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100