aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2020-11-02 14:22:33 +0100
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2020-11-02 14:22:33 +0100
commit6f9c8e35ec66125a8d260fe78c108585bb16dfce (patch)
tree5ce5b1b31dce8335973e88dfa84597b1360157f3
parent5ebeccb73f4373875ebf2418df4a9352373ee922 (diff)
removed hash function as parameter
Trillian doesn't give us much of a choice, see [1].
-rw-r--r--markup/api.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/markup/api.md b/markup/api.md
index d9286bf..d21649f 100644
--- a/markup/api.md
+++ b/markup/api.md
@@ -21,7 +21,6 @@ A log is defined by the following immutable parameters:
- Log identifier: `SHA256(public key)`, see RFC 6962
[§3.2](https://tools.ietf.org/html/rfc6962#section-3.2)
- Public key: DER encoding of the key represented as `SubjectPublicKeyInfo`
-- Hash algorithm: used to maintain the log's Merkle tree, e.g., SHA256
- Supported signature algorithms: a list of signature algorithms that the
log recognizes. Possible values are defined in RFC 8446,
[§4.2.3](https://tools.ietf.org/html/rfc8446#section-4.2.3). Submitters must
@@ -36,6 +35,9 @@ Note that **there is no MMD**. The idea is to merge added entries as soon as
possible, and no client should trust that something is logged until an inclusion
proof can be provided that references a trustworthy STH.
+Moreover, we use the same hash strategy as described in RFC 6962: SHA256 with
+`0x00` as leaf node prefix and `0x01` as interior node prefix.
+
## Minimum acceptance criteria
A log should accept a submission if it is:
- Well-formed, see below.