onepub-dev / onepub-dev/reVault
provide an api so apps can get access to a secret securely.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
Currently getting a secret out of a lockbox and into a third party app tends to cause it to be exposed.
At the least it is written to a file in plain text.
Is it practical for us to create an api that allows third party apps to access a secret without the secret leaving secure memory perhaps by a mmap file which is mlocked.
their is still the issue of how the user gets access to the vaults password.
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
No files, tests, or entry points are identified in the issue. Start by reviewing the existing vault and password-handling implementation, then clarify the API and secure-memory requirements; done means third-party apps can access a secret without it being written in plain text and the vault-password flow is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100