aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordec05eba <dec05eba@protonmail.com>2018-04-29 13:22:37 +0200
committerdec05eba <dec05eba@protonmail.com>2020-08-18 23:25:46 +0200
commita43c7ba9fa28b04dab3ba1f77a9428b6cc26003d (patch)
tree4489fcb6582aeff4c89a9ed73272a09686efc9ef
parenta14ec8d03587a60123ac6a27d93bfad118427639 (diff)
Remove implemented todo
-rw-r--r--README.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/README.md b/README.md
index abe8a0d..5e62b91 100644
--- a/README.md
+++ b/README.md
@@ -20,8 +20,6 @@ If we are spammed with the same key pair, we can ban messages that comes from th
which would take some time (we can make key generation take 60 seconds).
## Error handling
Currently operations are executed without knowing if they succeed or not. Operations should be modified to perhaps return std::future or use a callback function which is called with the operation result.
-## Safely store private keys
-Use Argon2 to store private keys
## Authorization
Verify the user that uses 'add' operation belongs to a group with write access to the key. If authorization fails, store the request
for a period of time since the request can be received before we have got the request to add user to the group with write access for the key.