oxidecomputer / oxidecomputer/sush
Automatically migrate ramdisk records to encrypted storage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 11
Description
Jobs run prior to TQ write into ramdisk records (because that's what's available), and when it comes up we write new records into /crypt/debug/*, but we currently don't move from the former to the latter. But we should, because otherwise those records are lost on reboot.
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
Locate the code that writes job records to the ramdisk and the code that writes new records under /crypt/debug/*. Start by tracing startup and reboot-related record handling, then determine how existing ramdisk records should be moved into encrypted storage; done means pre-TQ records are preserved after reboot and new records continue using the encrypted location.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100