diff options
| author | Rasmus Dahlberg <rasmus.dahlberg@kau.se> | 2021-10-07 19:15:22 +0200 |
|---|---|---|
| committer | Rasmus Dahlberg <rasmus.dahlberg@kau.se> | 2021-10-07 19:15:22 +0200 |
| commit | bb118ec24bea9de70ea0b3858e8f89badfe12023 (patch) | |
| tree | 0cda8e5065f8ae3a3a8a2c26a02b7382bec2c655 | |
| parent | 12bde236c6e156c2ad41a27109ebe091a184509c (diff) | |
used the same examples on website and design.md
| -rw-r--r-- | README.md | 4 | ||||
| -rw-r--r-- | doc/design.md | 3 |
2 files changed, 3 insertions, 4 deletions
@@ -10,8 +10,8 @@ TLS certificates keeps the overall design simple and generally useful. A minimal statement encodes the following claim: the right data has a certain cryptographic hash. You can add additional meaning to each statement. For example, you may use a sigsum log to claim things like -(i) everyone get the same news articles, -(ii) software package X builds reproducibly, or +(i) everyone gets the same executable binaries, +(ii) a domain does not serve malicious javascript, or (iii) a list of key-value pairs is maintained with policy Y. Sigsum logging makes it reasonable to believe a claim by adding enough diff --git a/doc/design.md b/doc/design.md index d1f7864..9081881 100644 --- a/doc/design.md +++ b/doc/design.md @@ -48,8 +48,7 @@ Examples include: [\[BT\]](https://wiki.mozilla.org/Security/Binary_Transparency) - A domain does not serve malicious javascript [\[SRI\]](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) -- A trust anchor behaves according to some policy - [\[nusenu-draft\]](https://gitlab.torproject.org/nusenu/torspec/-/blob/simple-wot-for-relay-operator-ids/proposals/ideas/xxx-simple-relay-operator-wot.md#a-simple-web-of-trust-for-tor-relay-operator-ids). +- A list of key-value pairs is maintained with a certain policy. There are many other use-cases that sigsum logging can help with. We intend to document them based on what people are working on in a |