diff options
| author | elijah <elijah@riseup.net> | 2013-08-14 03:31:44 -0700 |
|---|---|---|
| committer | elijah <elijah@riseup.net> | 2013-08-14 03:31:44 -0700 |
| commit | 31771838fb78f98e9cf60a6374e0c44735a5dc8d (patch) | |
| tree | 4b5beaec78bdcd58fa54f84f881fd433179d94b0 /docs/design/soledad.md | |
| parent | 442b94d9599f73efa90de3f2740ec51c1692e2c8 (diff) | |
soledad - clarify that it is verify first, then decrypt!
Diffstat (limited to 'docs/design/soledad.md')
| -rw-r--r-- | docs/design/soledad.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/design/soledad.md b/docs/design/soledad.md index 669437a..d200859 100644 --- a/docs/design/soledad.md +++ b/docs/design/soledad.md @@ -146,10 +146,11 @@ Other variables: * `document_secret`: equal to `HMAC(doc_id, storage_secret)`. This value is unique for every document and only kept in memory. We use document_secret instead of simply storage_secret in order to hinder possible derivation of storage_secret by the server. Every `doc_id` is unique. * `content`: equal to `sym_decrypt(cipher, ciphertext, document_secret)`. -When receiving a document with the above structure from the server, Soledad client will decrypt the `ciphertext` to find `content`, verify that the mac is correct, and then store `content` as a cleartext document in the local database replica. +When receiving a document with the above structure from the server, Soledad client will first verify that `mac` is correct, then decrypt the `ciphertext` to find `content`, which it saves as a cleartext document in the local database replica. -TO DO: determine supported ciphers -TO DO: determine HMAC method +TO DO: specify supported ciphers + +TO DO: specify supported HMAC Document synchronization ----------------------------------- |