summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2016-08-30 19:39:04 -0400
committerJoey Hess <joeyh@joeyh.name>2016-08-30 19:39:04 -0400
commit974e216f01e655a4e310627a9d26e8843225958c (patch)
tree41012d453409c338fd06d46f8c6f5598cab3f429
parent15ea23acdb00fa964d91d440274e3a78bd115083 (diff)
downloadkeysafe-974e216f01e655a4e310627a9d26e8843225958c.tar.gz
prioritize
-rw-r--r--TODO19
1 files changed, 14 insertions, 5 deletions
diff --git a/TODO b/TODO
index 4abdb42..4b1e2ef 100644
--- a/TODO
+++ b/TODO
@@ -1,9 +1,17 @@
-* improve restore progress bar points (update after every hash try)
-* If we retrieved enough shares successfully, but decrypt failed, must
- be a wrong password, so prompt for re-entry and retry with those shares.
+Soon:
+
* client/server Proof Of Work
* Include an example tor hidden service config, and systemd service file
for the server.
+* Get some keysafe servers set up.
+* .desktop file
+* Run --uploadqueued periodically (systemd timer?)
+
+Later:
+
+* improve restore progress bar points (update after every hash try)
+* If we retrieved enough shares successfully, but decrypt failed, must
+ be a wrong password, so prompt for re-entry and retry with those shares.
* Don't require --totalshares and --neededshares on restore when unusual
values were used for backup. Instead, probe until enough shares are found
to restore.
@@ -16,8 +24,9 @@
* --name and --othername to allow specifying those at the command line,
bypassing the prompts. With these and --key-value, keysafe would only
prompt for the password.
-* .desktop file
-* Run --uploadqueued periodically (systemd timer?)
+
+Wishlist:
+
* Keep secret keys in locked memory until they're encrypted.
(Raaz makes this possible to do.)
Would be nice, but not super-important, since gpg secret keys