aboutsummaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* add .md suffixRasmus Dahlberg2022-07-213-0/+0
|
* add renaming proposalRasmus Dahlberg2022-07-211-0/+23
|
* add proposal to drop "sigsum/v0" criteriaRasmus Dahlberg2022-07-211-0/+12
|
* Merge branch 'main' of git.sigsum.org:sigsumRasmus Dahlberg2022-07-211-0/+32
|\
| * add proposalLinus Nordberg2022-07-201-0/+32
| |
* | add replace domain hint with rate limit proposalRasmus Dahlberg2022-07-201-0/+33
| |
* | add permit lack of witness cosignatures proposalRasmus Dahlberg2022-07-201-0/+13
|/
* add hex-encoding proposalRasmus Dahlberg2022-07-201-0/+13
|
* minor grammar editRasmus Dahlberg2022-04-291-1/+1
|
* change 'verification_key' to 'public_key'Linus Nordberg2022-04-292-18/+18
| | | | | | | | Critically in the API: verification_key -> public_key Less critical in describing text, changing "verification key" and "verification public key" to "public key" all over. Issue: #40
* change 'preimage' to 'message'Linus Nordberg2022-04-292-12/+13
| | | | | | | Also, change 'checksum_hash' to 'checksum' to follow terminology in code, and general language. Issue: #40
* add proposal to simplify ascii namesRasmus Dahlberg2022-04-071-0/+21
|
* add proposalLinus Nordberg2022-04-051-0/+109
|
* added how sigsum compares to sigstore in faqRasmus Dahlberg2022-03-191-1/+6
|
* updated future work FAQRasmus Dahlberg2022-03-131-11/+41
|
* complete renaming of get-tree endpointsLinus Nordberg2022-03-031-1/+1
| | | | cf commit a242308c
* add shard hint to tree_leaf structLinus Nordberg2022-03-021-10/+8
| | | | | | Needed for being able to verify signatures. Also, remove struct statement since we won't expose it and have no use for it.
* redefined base url as log urlRasmus Dahlberg2022-02-131-15/+15
| | | | See details in proposals/2022-01-log-url.
* minor edits to the accepted log url proposalRasmus Dahlberg2022-02-131-8/+5
| | | | | - Remove final "/" from log URL definition (more readable API doc) - Resolve XXX that ln5 looked in to a while back (don't be strict).
* changed terminology to end-userRasmus Dahlberg2022-02-134-29/+29
| | | | See details in proposals/2022-02-end-user-terminology.md.
* persisted pads from meeting minutesRasmus Dahlberg2022-02-081-0/+21
|
* minor wording tweaks and fixesRasmus Dahlberg2022-01-312-33/+37
| | | | The majority of this commit is from ln5, thank you.
* fixed documentation issue regarding shard intervalRasmus Dahlberg2022-01-312-10/+11
|
* documented the decided ssh signature formatRasmus Dahlberg2022-01-312-66/+76
| | | | Refer to doc/proposals/2021-11-ssh-signature-format.md for details.
* documented decided get-tree-head endpoint proposalRasmus Dahlberg2022-01-312-44/+28
| | | | | | | | | Refer to doc/proposals/2022-01-tree-head-endpoint doc/proposals/2022-01-no-quick-tree-head-endpoint for details.
* documented the decided remove arbitrary bytes proposalRasmus Dahlberg2022-01-312-16/+32
| | | | | | | | | | Refer to doc/proposals/2021-11-remove-arbitrary-bytes.md for details. Since our proposal left the exact terminology undefined, this commit took a stab at that. The main idea was to keep referring to what we have in a leaf and what is being signed as a _checksum_. This ensures that we are not undermining or stepping away from our core of "signed checksums". It seemed quite natural to refer to a checksum's preimage.
* changed status from open to decidedRasmus Dahlberg2022-01-311-1/+1
| | | | See decision in archive/2022-01-04--meeting-minutes.
* added note about naming in a decided proposalRasmus Dahlberg2022-01-311-0/+3
|
* documented the decided add-leaf endpoint proposalRasmus Dahlberg2022-01-312-8/+10
| | | | Refer to doc/proposals/2022-01-add-leaf-endpoint for details.
* documented the decided domain hint proposalRasmus Dahlberg2022-01-312-3/+10
| | | | Refer to doc/proposals/2022-01-domain-hint for details.
* documented the decided get-* endpoint proposalRasmus Dahlberg2022-01-312-26/+29
| | | | Refer to archive/doc/proposals/2022-01-get-endpoints for details.
* moved some persisted pads to proposal directoryRasmus Dahlberg2022-01-316-0/+372
| | | | See doc/proposals/2022-01-how-to-use-proposal-folder for details.
* persisted pads from meeting minutesRasmus Dahlberg2022-01-252-0/+63
|
* re-opened remove-arbitrary-bytes proposalRasmus Dahlberg2021-12-221-1/+1
| | | | It did not become part of the SSH signing format proposal after all.
* fixed typoRasmus Dahlberg2021-12-051-3/+3
|
* added proposal into main documentationRasmus Dahlberg2021-12-043-12/+16
| | | | Sigsum logs should now use open-ended shard intervals.
* added aborted statusRasmus Dahlberg2021-12-041-9/+13
| | | | | We get the remove arbitrary bytes proposal "for free" when switching to a signing format that is backwards-compatible with SSH signatures.
* added to-be-implemented statusRasmus Dahlberg2021-12-041-7/+9
| | | | We decided to implement open-ended shard interval on 2021-11-23.
* update ssh signing format proposalLinus Nordberg2021-11-301-39/+126
|
* add textLinus Nordberg2021-11-161-0/+140
| | | | | Punting on all crypto agility for now. Let's make a separate proposal out of the contents of the section "Related questions".
* added remove arbitrary bytes proposalRasmus Dahlberg2021-11-151-0/+32
|
* added open-ended shard interval proposalRasmus Dahlberg2021-11-151-0/+34
|
* add placeholder for the ssh sig format ideaLinus Nordberg2021-11-151-0/+0
|
* added project launch linkRasmus Dahlberg2021-10-131-1/+1
|
* reordered shard hint and domain hint in §4Rasmus Dahlberg2021-10-131-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 typoRasmus Dahlberg2021-10-131-1/+1
|
* added history.md documentRasmus Dahlberg2021-10-131-0/+38
|
* defined what type of hex encoding is permittedRasmus Dahlberg2021-10-121-4/+4
|
* cleaned-up more questions sectionRasmus Dahlberg2021-10-121-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 enforcementRasmus Dahlberg2021-10-121-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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-21 21:39:24 +0000