docs: update
This commit is contained in:
parent
c032abe728
commit
2a19b21da1
@ -20,6 +20,7 @@ pash
|
||||
* [Dependencies](#dependencies)
|
||||
* [Usage](#usage)
|
||||
* [FAQ](#faq)
|
||||
* [How does this differ from `pass` or etc?](#how-does-this-differ-from-pass-or-etc)
|
||||
* [Where are passwords stored?](#where-are-passwords-stored)
|
||||
* [TODO](#todo)
|
||||
|
||||
@ -63,6 +64,12 @@ OPTIONS
|
||||
|
||||
## FAQ
|
||||
|
||||
### How does this differ from `pass` or etc?
|
||||
|
||||
I was looking for a CLI password manager (*written in `bash`*) and wasn't happy with the options I had found. They either had multiple instances of `eval` (*on user inputted data*), lots of unsafe `bash` (*no where near being `shellcheck` compliant.*) or they were overly complex. The opposites for what I'd want in a password manager.
|
||||
|
||||
I decided to write my own. `pash` is written in pure `bash` (*minus `gpg`, `mkdir` and optionally `xclip`.*) and the codebase is minimal (*150~ lines*). `gpg` is used to generate passwords and store the generated passwords in encrypted files.
|
||||
|
||||
### Where are passwords stored?
|
||||
|
||||
The passwords are store in GPG encrypted files located at `${XDG_DATA_HOME:=$HOME/.local/share}/pash}`.
|
||||
|
Loading…
Reference in New Issue
Block a user