| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | added remove arbitrary bytes proposal | Rasmus Dahlberg | 2021-11-15 | 1 | -0/+32 | |
| | | ||||||
| * | added open-ended shard interval proposal | Rasmus Dahlberg | 2021-11-15 | 1 | -0/+34 | |
| | | ||||||
| * | add placeholder for the ssh sig format idea | Linus Nordberg | 2021-11-15 | 1 | -0/+0 | |
| | | ||||||
| * | added meeting minutes | Rasmus Dahlberg | 2021-11-09 | 1 | -0/+34 | |
| | | ||||||
| * | persisted pads from meeting minutes | Rasmus Dahlberg | 2021-11-09 | 2 | -0/+115 | |
| | | ||||||
| * | added meeting minutes | Rasmus Dahlberg | 2021-11-02 | 1 | -0/+35 | |
| | | ||||||
| * | added meeting minutes | Rasmus Dahlberg | 2021-10-26 | 1 | -0/+41 | |
| | | ||||||
| * | added meeting minutes | Rasmus Dahlberg | 2021-10-19 | 1 | -0/+74 | |
| | | ||||||
| * | persisted pads from meeting minutes | Rasmus Dahlberg | 2021-10-19 | 2 | -0/+129 | |
| | | ||||||
| * | added project launch link | Rasmus Dahlberg | 2021-10-13 | 1 | -1/+1 | |
| | | ||||||
| * | reordered shard hint and domain hint in §4 | Rasmus Dahlberg | 2021-10-13 | 1 | -22/+22 | |
| | | | | | | | After our refactor rate limits are no longer mentioned in §3. The domain hint subsection contains that text now, and should therefore be before the shard hint subsection that assumed it is already explained. | |||||
| * | fixed typo | Rasmus Dahlberg | 2021-10-13 | 1 | -1/+1 | |
| | | ||||||
| * | added history.md document | Rasmus Dahlberg | 2021-10-13 | 1 | -0/+38 | |
| | | ||||||
| * | defined what type of hex encoding is permitted | Rasmus Dahlberg | 2021-10-12 | 1 | -4/+4 | |
| | | ||||||
| * | merged documentation improvements from ln5/rgdd | Rasmus Dahlberg | 2021-10-12 | 2 | -118/+144 | |
| |\ | ||||||
| | * | cleaned-up more questions section | Rasmus Dahlberg | 2021-10-12 | 1 | -5/+1 | |
| | | | | | | | | | | | | | | | | | | | These questions are to some extent answered as part of our refactor, or addressed as things we are still open to think more about. I think we can leave them out for now and add them later _with answers_ if needed. I kept the privacy concerns question because that is not addressed anywhere yet. We think that the answer is "mostly none". | |||||
| | * | removed comments about partial enforcement | Rasmus Dahlberg | 2021-10-12 | 1 | -10/+0 | |
| | | | | | | | | | | | | | | | To be re-added at a later time somewhere else. It is not helpful for a reader that is trying to understand the basic design for the first time. Spotted by ln5. | |||||
| | * | spelled out FOSS project correctly | Rasmus Dahlberg | 2021-10-12 | 1 | -3/+3 | |
| | | | | | | | | | Spotted by ln5. | |||||
| | * | removed mention of Go modules | Rasmus Dahlberg | 2021-10-12 | 1 | -1/+1 | |
| | | | | | | | | | | | Strictly speaking the logged data structure is a checksum of a Go module. This could be confusing with the wording of this sentence. | |||||
| | * | renamed section 4.4 | Rasmus Dahlberg | 2021-10-12 | 1 | -1/+1 | |
| | | | | | | | | | Discussed with ln5. | |||||
| | * | minor wording | Linus Nordberg | 2021-10-12 | 1 | -6/+6 | |
| | | | ||||||
| | * | added additional witnessing thoughts in FAQ | Rasmus Dahlberg | 2021-10-10 | 1 | -4/+22 | |
| | | | ||||||
| | * | emphasized "attacker" instead of "log operator" | Rasmus Dahlberg | 2021-10-10 | 1 | -2/+2 | |
| | | | ||||||
| | * | explained property of usage pattern that relates to sharding | Rasmus Dahlberg | 2021-10-10 | 1 | -5/+13 | |
| | | | ||||||
| | * | fixed overflowing lines, no content changes | Rasmus Dahlberg | 2021-10-10 | 2 | -44/+55 | |
| | | | ||||||
| | * | added a few minor edits | Rasmus Dahlberg | 2021-10-10 | 2 | -16/+14 | |
| | | | ||||||
| | * | keep summary session at its current location | Rasmus Dahlberg | 2021-10-10 | 1 | -1/+0 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | I don't think it improves our design document by being moved. We already have a summary of properties in the introduction, and an easier primer at the start of Section 3 that is strongly coupled to Figure 1. Perhaps it is no longer necessary though. When we wrote this we did not have a summary of properties in introduction, or a relatively detailed walk-through of the log's intended usage-pattern. I'm fine with both keeping as is or deleting if it feels redundant. | |||||
| | * | reworked partial enforcement of verification criteria | Rasmus Dahlberg | 2021-10-10 | 1 | -9/+10 | |
| | | | | | | | | | | | - Expanded into two separate examples - Moved it into the verification subsection | |||||
| | * | refactored extended domain hint text into FAQ | Rasmus Dahlberg | 2021-10-10 | 1 | -21/+22 | |
| | | | ||||||
| | * | fixed small/medium issues and left some comments | Linus Nordberg | 2021-10-10 | 1 | -63/+67 | |
| | | | | | | | | | | | | | | | | | | | | | - Deleted unnecessary roadmap - Clarified distribution and verification section - Proposed down-to-the-point text for domain hint description - Left comments that we should consider addressing - A bunch of minor edits For transparency this commit was squashed and rebased by rgdd. | |||||
| * | | added meeting minutes | Rasmus Dahlberg | 2021-10-12 | 1 | -0/+42 | |
| |/ | ||||||
| * | updated terminology that was lagging behind | Rasmus Dahlberg | 2021-10-10 | 2 | -22/+24 | |
| | | | | | | | | | | - s/verifier/monitor - s/claimant/signer - s/believer/verifier - s/opaque data/data - minor rewordings related to these substitutions - referenced a possible timestamp usage | |||||
| * | refactored services to only be a contact session | Rasmus Dahlberg | 2021-10-10 | 1 | -16/+11 | |
| | | ||||||
| * | fixed rendering error on cgit | Rasmus Dahlberg | 2021-10-07 | 1 | -0/+1 | |
| | | ||||||
| * | simplified website text | Rasmus Dahlberg | 2021-10-07 | 1 | -22/+21 | |
| | | | | | | | | | More emphasis on what a sigsum log actually provides, and less emphasis on the details about how one can think about the cool use-cases that are possible on-top of a sigsum log. Just list relatable examples instead. Also fixed capitalization typos for Sigsum, "the project". | |||||
| * | used the same examples on website and design.md | Rasmus Dahlberg | 2021-10-07 | 2 | -4/+3 | |
| | | ||||||
| * | emphasized that monitors look for unwanted key-usage | Rasmus Dahlberg | 2021-10-07 | 2 | -1/+1 | |
| | | ||||||
| * | removed unnecessary sentence in threat model | Rasmus Dahlberg | 2021-10-07 | 2 | -4/+3 | |
| | | ||||||
| * | fixed bad formulation | Rasmus Dahlberg | 2021-10-07 | 1 | -2/+2 | |
| | | ||||||
| * | added example of non-scope in our architecture | Rasmus Dahlberg | 2021-10-07 | 1 | -2/+4 | |
| | | ||||||
| * | refactored Figure 1 and primer text | Rasmus Dahlberg | 2021-10-07 | 1 | -37/+34 | |
| | | | | | | - Added anti-spam mechanism, completes figures without too much clutter - Minor rewordings that simplified description | |||||
| * | fixed s/transparent log/transparency log/g | Rasmus Dahlberg | 2021-10-07 | 2 | -9/+9 | |
| | | ||||||
| * | expressed goal without higher-level use-cases in mind | Rasmus Dahlberg | 2021-10-07 | 1 | -6/+2 | |
| | | ||||||
| * | refactored abstract to better describe sigsum logging | Rasmus Dahlberg | 2021-10-07 | 1 | -5/+8 | |
| | | ||||||
| * | rephrased "the right data" pitch | Rasmus Dahlberg | 2021-10-07 | 2 | -3/+3 | |
| | | | | | | | | There is a risk that "the right data" is confused with "what do you mean, obviously it is the right data if there is a valid signature". Tried just reword. | |||||
| * | added a major refactor of design.md | Rasmus Dahlberg | 2021-10-05 | 1 | -268/+270 | |
| | | | | | | | | | | | | | | The claimant model was mostly pulled from this document. It is useful to define use-cases of sigsum in a succinct way, but not helpful to tell the reader about the concrete design that we have for a sigsum log. (We still have a separate document that uses the claimant model.) This refactor also tries to remove focus from use-cases that in general are messy, and instead focus on the simple sigsum logging design that has a very well-defined and thought-through usage-pattern. The result of this is that things should be a little bit more down-to-the-point. | |||||
| * | persisted meeting minutes | Rasmus Dahlberg | 2021-10-05 | 1 | -0/+65 | |
| | | ||||||
| * | persisted pads from meeting minutes | Rasmus Dahlberg | 2021-10-05 | 2 | -0/+67 | |
| | | ||||||
| * | added issue about risk-averse attacker (design.md) | Rasmus Dahlberg | 2021-10-02 | 1 | -0/+15 | |
| | | ||||||
| * | updated claimant model examples | Rasmus Dahlberg | 2021-10-02 | 1 | -64/+24 | |
| | | | | | | | | | | I think the claimant model is most helpful for us to describe the different use-cases of a sigsum log. Let's focus on claimant models for use-cases in this document, not claimant models for logs _as well_. I kept R-B as an example because it is concrete, and fixed the long-due updates that GeKo pointed out a while back about, e.g., "right data". | |||||
 |
index : sigsum | |
| Moved to https://git.glasklar.is/sigsum/project/documentation | Sigsum crew |
| aboutsummaryrefslogtreecommitdiff |