From 9288886de0e4477bb6e3dface9266fe0644b3e97 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Thu, 7 Oct 2021 15:27:19 +0200 Subject: expressed goal without higher-level use-cases in mind --- doc/design.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) (limited to 'doc/design.md') 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 -- cgit v1.2.3