clortho

commit 409ed88fd61964d95b2efa12a2d1ab0347058362
parent 3046cf20b0f11c0f0dfaf35658d302dad7d6bbba
Author: lash <dev@holbrook.no>
Date:   Tue, 11 Jan 2022 12:53:06 +0000

Improve readme

Diffstat:
M
clortho.sh
 | 
4
++--
M
readme.txt
 | 
10
++++++++++

2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/clortho.sh b/clortho.sh
@@ -28,10 +28,10 @@ set +e
 passphrase=${CLORTHO_PASSPHRASE:-$PASSPHRASE}
 if [ -z "$passphrase" ]; then
 	stty -echo
-	echo -n "?> "
+	echo -n "passphrase: "
 	read passphrase
-	echo
 	stty echo
+	echo
 fi
 
 
diff --git a/readme.txt b/readme.txt
@@ -6,4 +6,14 @@ The key is stored as sha256 of passphrase || key.
 
 The value is symmetrically encrypted with passphrase. (the bash prototype uses ccrypt)
 
+The passphrase is given by setting the env var CLORTHO_PASSPHRASE
+
+To set:
+
+bash clortho.sh foo bar
+
+To get:
+
+bash clortho.sh foo
+
 This script it NOT SAFE for production use because it leaks password to process lists and tmpfs while executing. However, the key/value pairs, once produced, are safe to store.