aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/.design.md.swpbin0 -> 36864 bytes
-rw-r--r--doc/design.md7
2 files changed, 3 insertions, 4 deletions
diff --git a/doc/.design.md.swp b/doc/.design.md.swp
new file mode 100644
index 0000000..8d9f93a
--- /dev/null
+++ b/doc/.design.md.swp
Binary files differ
diff --git a/doc/design.md b/doc/design.md
index b177f85..57bc919 100644
--- a/doc/design.md
+++ b/doc/design.md
@@ -130,10 +130,9 @@ Transparency Log
[\[DigiCert\]](https://groups.google.com/a/chromium.org/g/ct-policy/c/aKNbZuJzwfM).
The overall system is said to be secure if a monitor can discover every signed
-checksum that a verifier would accept, or alternatively, if log misbehavior can
-be detected. A log can misbehave by not presenting the same append-only Merkle
-tree to everyone. A log operator would only do that if it is likely to go
-unnoticed.
+checksum that a verifier would accept. A log can misbehave by not presenting
+the same append-only Merkle tree to everyone because it is attacker-controlled.
+However, a log operator would only do that if it is likely to go unnoticed.
For security we need a collision resistant hash function and an unforgeable
signature scheme. We also assume that at most a threshold of independent