oxidecomputer / oxidecomputer/hubris
Turn TrustZone isolation back on in RoT or convince ourselves it's not necessary.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
TZ isolation is currently off in the RoT builds and support has been removed (except for version control history, of course).
We will almost certainly want to turn it back on in a slightly re-imagined post-bootleby form. This is intended as a tracking issue for that work.
Contributor guide
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 reviewing the RoT build configuration and the version-control history where TrustZone support was removed. Determine whether a post-bootleby isolation design is needed and document the decision; if it is, the work is complete when isolation is restored in the RoT builds with the revised design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100