aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authordec05eba <dec05eba@protonmail.com>2018-03-05 22:45:56 +0100
committerdec05eba <dec05eba@protonmail.com>2020-08-18 23:25:46 +0200
commiteda9a7bbefc5587bf1ff895a9214f450e64575fa (patch)
tree0f968fb7373a29cf116b4b6d473a966e28e62825 /README.md
parent33e823ddddddd4a13b1a05b90ae5b419b89bcb1d (diff)
Implement 'create' operation, add seeding
Seeding is currently only done on the key you specify, in the future the user should request data that it can seed.
Diffstat (limited to 'README.md')
-rw-r--r--README.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/README.md b/README.md
index 8db5819..d5035d5 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,9 @@
# odhtdb
Decentralized key-value database using OpenDHT for decentralized communication.
## End-to-end encryption
-Data is signed using ed25519 and encrypted using XChaCha20. See src/Encryption.cpp and src/Signature.cpp.
-
+Data is signed using ed25519, encrypted using xchacha20-poly1305 ietf and hashed using Blake2b.
+See src/Encryption.cpp, src/Signature.cpp and src/Hash.cpp.
+Also check Scheme.md for packet construction.
# Limits
Only 65kb of data can be used for each `add`. You can add more data by using `add` several times.
User and group name can't be longer than 255 characters.
@@ -21,3 +22,5 @@ for a period of time since the request can be received before we have got the re
This can happen because we dont verify all peers get the data so by the time one peer gets the data, they could have got other data from us
(depends on network routing, network speed etc). Out of order requests also allows the network to operate faster.
Operations are parsed in order for the receiving peer using operation timestamp.
+## Padding
+Packets should have padding in the encrypted data to prevent peers without encryption key to analyze content