From d745cc8c1fdfc2f7ca607bfeefa5aefd1ae5a2a2 Mon Sep 17 00:00:00 2001 From: Dylan Araps Date: Fri, 24 May 2019 11:26:46 +0300 Subject: [PATCH] docs: update --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f915bd9..64ad6b5 100644 --- a/README.md +++ b/README.md @@ -58,7 +58,7 @@ COMMANDS ### 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 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` (*nowhere 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 (*100~ lines*). `gpg` is used to generate passwords and store the generated passwords in encrypted files.