onepub-dev / onepub-dev/reVault
allow different security settings on identities
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
Current the security settings such as auto login are per vault.
It might be useful to make these per identity.
For example I might have a dev and a production identity.
For dev I want auto login, for production I only want to unlock the vault as required.
Currently the vault has a single password. This sort of scheme would require that an identity had a password as well.
It would require each command to recognize that the identity required a password and prompt the user accordingly.
We could do this via letting the user create multiple vaults but that seems more kludgy as it would require them to have separate contact lists.
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 or tests are named. Start by locating the vault-level security settings and command handling, then trace how identities and passwords are represented. Done means security settings can differ per identity, identity passwords are handled, and commands prompt when the selected identity requires unlocking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100