From a41cbda751d515032859d72656fda3d219300ecb Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 14 Sep 2016 16:42:26 -0400 Subject: Store information about backed up keys in ~/.keysafe/backup.log This can be deleted by the user at any time, but it's useful in case a server is known to be compromised, or a problem is found with keysafe's implementation that makes a backup insecure. This commit was sponsored by Nick Daly on Patreon. --- TODO | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) (limited to 'TODO') diff --git a/TODO b/TODO index 58de1e6..54593b2 100644 --- a/TODO +++ b/TODO @@ -4,11 +4,7 @@ Soon: harder for traffic analysis to tell that it's keysafe traffic. * Implement the different categories of servers in the server list. * Get some keysafe servers set up. -* Keep a local record of keys that have been backed up, and the tunables - and password entropy. This will allow warning later if the crack estimate - has to be revised downward for some reason, or if a server is - compromised. -* Run --uploadqueued periodically (systemd timer?) +* Run --uploadqueued periodically (systemd timer or desktop autostart?) Later: -- cgit v1.2.3