summaryrefslogtreecommitdiff
path: root/design-documents
diff options
context:
space:
mode:
authorFlorian Dold <florian@dold.me>2021-04-12 19:25:34 +0200
committerFlorian Dold <florian@dold.me>2021-04-12 19:25:34 +0200
commit1851c8f16ed73f8ca16be71577ed7dc7cf92b5df (patch)
tree67295bcee755953a8e49d0a34b8a15ca6555417f /design-documents
parentca3829f6b7afc32c4963b39ebdbc4f81fb9fbf91 (diff)
downloaddocs-1851c8f16ed73f8ca16be71577ed7dc7cf92b5df.tar.gz
docs-1851c8f16ed73f8ca16be71577ed7dc7cf92b5df.tar.bz2
docs-1851c8f16ed73f8ca16be71577ed7dc7cf92b5df.zip
minor question clarification
Diffstat (limited to 'design-documents')
-rw-r--r--design-documents/018-contract-json.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/design-documents/018-contract-json.rst b/design-documents/018-contract-json.rst
index ba4646f..2bc147b 100644
--- a/design-documents/018-contract-json.rst
+++ b/design-documents/018-contract-json.rst
@@ -155,7 +155,8 @@ Discussion / Q&A
use the global salt **and** the path of the forgettable field
as the salt for hashing.
-* Why do we require the 0-termination?
+* Why do we require the 0-termination in the hash / kdf? Doesn't seem to match what
+ e.g. ``shasum`` does.
* Why do we not supply any "info" string (= context chunks in the GNUNET_CRYPTO_kdf terminology)
to the hkdf? Does it matter?