onepub-dev / onepub-dev/reVault
vault review
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
Need to review how we are storing data in the vault.
- document the file format.
- ensure that private keys use our new secure heap.
- change the parsing of private keys to use secure memory all the way down - this may require us to enhance SecureString.
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 tracing vault storage and private-key parsing, then inspect SecureString and the new secure heap. Document the file format and verify that private-key data remains in secure memory throughout parsing; no files or tests are named, so identify the relevant tests before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, documentation, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100