summaryrefslogtreecommitdiffhomepage
path: root/TODO
Commit message (Collapse)AuthorAge
* move TODO to doc/todo, expand a few itemsJoey Hess2017-04-04
|
* move item from TODO to doc/todo and replyJoey Hess2017-04-04
|
* remove AONTJoey Hess2017-03-11
| | | | | | | | | | | | | | | If there are 3 chunks each split into 3 shares and distributed amoung 9 servers, and 2 shares are needed to recover each chunk, then with AONT, 6 servers need to collude to do so. Without AONT, a single chunk might contain the actual gpg private key, and only 3 servers might need to collude to recover that single chunk. On the other hand, with 9 servers, SSS can split the data into 9 shares with 6 needed for recovery. Thus, 6 servers will be needed to recover any data at all, no matter how it's chunked or which chunks contain the actual gpg key. So, I think that tuning SSS can provide the same effects as AONT.
* idea from Thomas SJoey Hess2017-03-11
|
* add better object-id derivation ideaJoey Hess2017-01-25
|
* todoJoey Hess2017-01-25
|
* Keysafe has a new website, https://keysafe.branchable.com/Joey Hess2017-01-22
|
* Better suggestion when user is having difficulty thinking of a strong enough ↵Joey Hess2016-11-06
| | | | | | password. This commit was sponsored by Ignacio on Patreon.
* results of a little bit of usability testingJoey Hess2016-11-05
|
* The third keysafe server is now available, provided by Purism.Joey Hess2016-10-24
| | | | | | Hoped this will be Recommended, but it's still being vetted. This commit was sponsored by Andreas on Patreon.
* updateJoey Hess2016-10-23
|
* Argon2dJoey Hess2016-10-18
|
* thoughtJoey Hess2016-10-06
|
* updateJoey Hess2016-10-06
|
* New --add-storage-directory and --add-server optionsJoey Hess2016-10-06
| | | | | | | | * New --add-storage-directory and --add-server options, which can be used to make keysafe backup/restore using additional locations. * Removed --store-local option; use --add-storage-directory instead. This commit was sponsored by Thomas Hochstein on Patreon.
* todoJoey Hess2016-10-05
|
* todoJoey Hess2016-09-27
|
* TODOJoey Hess2016-09-26
|
* Randomize the server list.Joey Hess2016-09-26
| | | | | | | May help avoid some correlations. Once there are many servers, will spread the load out amoung them. This commit was sponsored by Ethan Aubin.
* todoJoey Hess2016-09-22
|
* updateJoey Hess2016-09-22
|
* In --autostart mode, check for gpg keys that have not been backed up, and ↵Joey Hess2016-09-22
| | | | | | | | offer to back them up. Only ask once per key. This commit was sponsored by Thomas Hochstein on Patreon.
* Added --autostart mode and install FDO autostart fileJoey Hess2016-09-22
| | | | | | | | | | | | | | | | | | | | --autostart mode currently only uploads queued keys, but it will later be expanded to do more. Including checking the BackupRecord for problems when necessary. The autostart file is installed by keysafe --backup, so that when keysafe is installed with stack, and used, it will make sure it autostarts in the future. The autostart file is installed by the Makefile too. This will later let --autostart check for keys that have not been backed up and prompt about backing them up. This way, the user won't need to remember to run keysafe to back things up. Reused Utility.FreeDesktop from git-annex, and had to add some stuff it depends on. This commit was sponsored by Fernando Jimenez on Patreon.
* todoJoey Hess2016-09-16
|
* TODOJoey Hess2016-09-15
|
* updateJoey Hess2016-09-14
|
* Store information about backed up keys in ~/.keysafe/backup.logJoey Hess2016-09-14
| | | | | | | | 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.
* rate limiting and PoW seem to work now!Joey Hess2016-09-14
|
* updateJoey Hess2016-09-13
|
* updateJoey Hess2016-09-13
|
* todoJoey Hess2016-09-13
|
* implemented dynamic rate limitingJoey Hess2016-09-13
|
* don't need --disk-reserveJoey Hess2016-09-13
| | | | keysafe does not run as root, so the normal ext2 disk reserve will do
* adding some server disk usage tuning optionsJoey Hess2016-09-13
|
* todoJoey Hess2016-09-13
|
* implement client-server Proof Of WorkJoey Hess2016-09-12
| | | | | | | | | | | | | | | | | | | Mashed up a argon2-based PoW with token buckets and bloom filters. This is intended to prevent a few abuses including: * Using a keysafe server for general file storage, by storing a whole lot of chunks. * An attacker guessing names that people will use, and uploading junk to keysafe servers under those names, to make it harder for others to use keysafe later. * An attacker trying to guess the names used for objects on keysafe servers in order to download them and start password cracking. (As a second level of defense, since the name generation hash is expensive already.) Completely untested, but it builds! This commit was sponsored by Andreas on Patreon.
* updateJoey Hess2016-09-04
|
* Added --name and --othername options.Joey Hess2016-09-04
|
* benchmark of full restore took expected amount of time on librem 13Joey Hess2016-09-01
|
* Fix bug that prevented keysafe --server from running when there was no ↵Joey Hess2016-09-01
| | | | controlling terminal and zenity was not installed.
* todo0.20160831Joey Hess2016-08-31
|
* add .desktop fileJoey Hess2016-08-31
|
* updateJoey Hess2016-08-31
|
* key encryption hash benchmark was off by a factor of 16, fixJoey Hess2016-08-30
| | | | | | f2fa457a7e45721e94a3f5d0307faf874150cdb4 did in fact fix a laziness issue in the benchmark. This explains why restore was taking so long, although I need to re-run a real restore to double-check this.
* addJoey Hess2016-08-30
|
* todoJoey Hess2016-08-30
|
* prioritizeJoey Hess2016-08-30
|
* Added basic test suite.Joey Hess2016-08-30
|
* formatJoey Hess2016-08-30
|
* Tuned argon2 hash parameters on better hardware than my fanless laptop.Joey Hess2016-08-30
| | | | | | | | | | | | | Used a Purism Librem 13. The name generation hash was already ok, but the key encryption key hash was quite off. This is not a total blazing top of the line server, but that's ok; keysafe's hashes are intended to be tuned for commodity hardware. It should not take a user more than an hour to restore a key. The spotAWS value is adjusted because AWS's c4.8xlarge instances run at up to 3.5Ghz, compared with the 2.20Ghz of the Librem 13. Basically it's one Moore's doubling ahead of the reference laptop.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-20 00:06:15 +0000