aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLinus Nordberg <linus@nordberg.se>2021-09-13 12:28:32 +0200
committerLinus Nordberg <linus@nordberg.se>2021-09-13 12:28:32 +0200
commit5be841d2a67e28b064275c9d0ff2516df8e94bf3 (patch)
tree6305266dba2090798dbaf89ab23f9aa5a5051d67
parent75573d4a62cd28462c818689158e2a28d5497e3f (diff)
make a bullet list oiut of the three claims
-rw-r--r--README.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/README.md b/README.md
index 8ef0d7c..57114c2 100644
--- a/README.md
+++ b/README.md
@@ -10,9 +10,10 @@ _certificates_ keeps the overall design simple and generally useful.
A minimal statement encodes the following claim: the data has cryptographic hash
X. You can add additional meaning to each statement. For example, you may use
a sigsum log to claim that
- _everyone gets the same news articles_,
- _software package X builds reproducibly_, or
- _a list of key-value pairs is maintained with policy Y_.
+
+- everyone gets the same news articles,
+- software package X builds reproducibly, or
+- a list of key-value pairs is maintained with policy Y.
Sigsum logging makes it reasonable to believe your claims by adding enough
discoverability to verify them.