From c5dd152a0b1ed45ed40c60f3bcf004fe7edb6ff0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 5 Nov 2016 18:00:29 -0400 Subject: results of a little bit of usability testing --- TODO | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/TODO b/TODO index 7ad9b49..105308f 100644 --- a/TODO +++ b/TODO @@ -2,12 +2,16 @@ Soon: * Finish vetting 2 servers to Recommended. * Set up --check-servers in a cron job, so I know when servers are down. +* If user is having difficulty thinking of good enough password, give + advice. Later: * The attack cost display can lead to a false sense of security if the user takes it as gospel. It needs to be clear that it's an estimate. This and other parts of the keysafe UI need usability testing. +* Make --gui password entry fields longer, so user does not feel they need + to make password short. (zenity may not allow configuring this) * 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. @@ -31,6 +35,12 @@ Later: Wishlist: +* Custom GUI, instead of zenity. Allows: + - Fewer screens by consolidating multiple prompts. + - Check same password entered second time and don't allow continuing + if not. + - Password strengh display, and don't allow continuing if password is too + weak. * 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 -- cgit v1.2.3