sigsum - Moved to https://git.glasklar.is/sigsum/project/documentation

	Commit message (Collapse)	Author	Age	Files	Lines
*	minor grammar edit	Rasmus Dahlberg	2022-04-29	1	-1/+1
\|
*	change 'verification_key' to 'public_key'	Linus Nordberg	2022-04-29	2	-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 Nordberg	2022-04-29	2	-12/+13
\| \| \| \| \| \| \|	Also, change 'checksum_hash' to 'checksum' to follow terminology in code, and general language. Issue: #40
*	add proposal to simplify ascii names	Rasmus Dahlberg	2022-04-07	1	-0/+21
\|
*	add proposal	Linus Nordberg	2022-04-05	1	-0/+109
\|
*	added how sigsum compares to sigstore in faq	Rasmus Dahlberg	2022-03-19	1	-1/+6
\|
*	updated future work FAQ	Rasmus Dahlberg	2022-03-13	1	-11/+41
\|
*	complete renaming of get-tree endpoints	Linus Nordberg	2022-03-03	1	-1/+1
\| \| \| \|	cf commit a242308c
*	add shard hint to tree_leaf struct	Linus Nordberg	2022-03-02	1	-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 url	Rasmus Dahlberg	2022-02-13	1	-15/+15
\| \| \| \|	See details in proposals/2022-01-log-url.
*	minor edits to the accepted log url proposal	Rasmus Dahlberg	2022-02-13	1	-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-user	Rasmus Dahlberg	2022-02-13	4	-29/+29
\| \| \| \|	See details in proposals/2022-02-end-user-terminology.md.
*	persisted pads from meeting minutes	Rasmus Dahlberg	2022-02-08	1	-0/+21
\|
*	minor wording tweaks and fixes	Rasmus Dahlberg	2022-01-31	2	-33/+37
\| \| \| \|	The majority of this commit is from ln5, thank you.
*	fixed documentation issue regarding shard interval	Rasmus Dahlberg	2022-01-31	2	-10/+11
\|
*	documented the decided ssh signature format	Rasmus Dahlberg	2022-01-31	2	-66/+76
\| \| \| \|	Refer to doc/proposals/2021-11-ssh-signature-format.md for details.
*	documented decided get-tree-head endpoint proposal	Rasmus Dahlberg	2022-01-31	2	-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 proposal	Rasmus Dahlberg	2022-01-31	2	-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 decided	Rasmus Dahlberg	2022-01-31	1	-1/+1
\| \| \| \|	See decision in archive/2022-01-04--meeting-minutes.
*	added note about naming in a decided proposal	Rasmus Dahlberg	2022-01-31	1	-0/+3
\|
*	documented the decided add-leaf endpoint proposal	Rasmus Dahlberg	2022-01-31	2	-8/+10
\| \| \| \|	Refer to doc/proposals/2022-01-add-leaf-endpoint for details.
*	documented the decided domain hint proposal	Rasmus Dahlberg	2022-01-31	2	-3/+10
\| \| \| \|	Refer to doc/proposals/2022-01-domain-hint for details.
*	documented the decided get-* endpoint proposal	Rasmus Dahlberg	2022-01-31	2	-26/+29
\| \| \| \|	Refer to archive/doc/proposals/2022-01-get-endpoints for details.
*	moved some persisted pads to proposal directory	Rasmus Dahlberg	2022-01-31	6	-0/+372
\| \| \| \|	See doc/proposals/2022-01-how-to-use-proposal-folder for details.
*	persisted pads from meeting minutes	Rasmus Dahlberg	2022-01-25	2	-0/+63
\|
*	re-opened remove-arbitrary-bytes proposal	Rasmus Dahlberg	2021-12-22	1	-1/+1
\| \| \| \|	It did not become part of the SSH signing format proposal after all.
*	fixed typo	Rasmus Dahlberg	2021-12-05	1	-3/+3
\|
*	added proposal into main documentation	Rasmus Dahlberg	2021-12-04	3	-12/+16
\| \| \| \|	Sigsum logs should now use open-ended shard intervals.
*	added aborted status	Rasmus Dahlberg	2021-12-04	1	-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 status	Rasmus Dahlberg	2021-12-04	1	-7/+9
\| \| \| \|	We decided to implement open-ended shard interval on 2021-11-23.
*	update ssh signing format proposal	Linus Nordberg	2021-11-30	1	-39/+126
\|
*	add text	Linus Nordberg	2021-11-16	1	-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 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 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
\|
*	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.
*	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.