aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-07 15:27:19 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-07 15:27:19 +0200
commit9288886de0e4477bb6e3dface9266fe0644b3e97 (patch)
tree9513140b1b8755dcf4dc48b372b6376303ee7d26
parentbd47c47dfd26706b5846b53addd4ea8066f03c44 (diff)
expressed goal without higher-level use-cases in mind
-rw-r--r--doc/design.md8
1 files changed, 2 insertions, 6 deletions
diff --git a/doc/design.md b/doc/design.md
index 66e953e..8c4e199 100644
--- a/doc/design.md
+++ b/doc/design.md
@@ -59,12 +59,8 @@ using the
This document is about our log design.
### 1.1 - Goals and non-scope
-The goal of sigsum logging is to be a building block that facilitates
-verification of falsifiable claims. There should be emphasis on _facilitating_,
-because all a sigsum log does is ensure that signed checksums are discoverable.
-
-We want to achieve our goal without making assumptions that are use-case
-specific. Therefore, sigsum logs allow logging of signed checksum and some
+The goal of sigsum logging is to make a signer's key-usage transparent in
+general. Therefore, sigsum logs allow logging of signed checksum and some
minimally required metadata. Storing data and rich metadata is a non-goal.
We want the resulting design to be easy from many different perspectives, for