taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 1851c8f16ed73f8ca16be71577ed7dc7cf92b5df
parent ca3829f6b7afc32c4963b39ebdbc4f81fb9fbf91
Author: Florian Dold <florian@dold.me>
Date:   Mon, 12 Apr 2021 19:25:34 +0200

minor question clarification

Diffstat:
Mdesign-documents/018-contract-json.rst | 3++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git 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?