Sigsum mailing lists
Sign In
Sign Up
Sign In
Sign Up
Manage this list
×
Keyboard Shortcuts
Thread View
j
: Next unread message
k
: Previous unread message
j a
: Jump to all threads
j l
: Jump to MailingList overview
2023
May
April
March
February
January
2022
December
November
October
September
August
July
June
May
April
March
February
January
2021
December
November
October
September
August
List overview
Download
Sigsum-general
October 2021
----- 2023 -----
May 2023
April 2023
March 2023
February 2023
January 2023
----- 2022 -----
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
----- 2021 -----
December 2021
November 2021
October 2021
September 2021
August 2021
sigsum-general@lists.sigsum.org
1 participants
1 discussions
Start a n
N
ew thread
Sigsum project launch
by Rasmus Dahlberg
Hi everyone, Today we are launching Sigsum, a free and open source software project that revolves around transparency logs and their applications. While most other logging efforts focus on concrete data structures like TLS certificates, sigsum logs are meant to be general building blocks that support signed checksums and minimally required metadata. It is up to the signer to determine what a checksum should represent. For example, Mozilla's take on Binary Transparency [1] fits into the intended use of sigsum logging. By avoiding the Certificate Transparency design, complexity can be reduced. Sigsum logging has no SCTs, complicated ASN.1 parsers, or reactive gossip-audit protocols. Minimalism, distributed trust, and centralized log operations make up our key pillars. These characteristics keep the attack surface small. They also simplify usage, operations, and verification of sigsum logs. To learn more about sigsum logging, please refer to our design and API documentation [2, 3]. There is also a public prototype available [4]. Would you like to be part of the conversation? We have open Jitsi meetings on Tuesdays at 11:00 UTC. Meeting minutes and linked pads are persisted in our archive for transparency and future reference [5]. Asynchronous interactions take place on IRC, Matrix, and email. Website:
https://www.sigsum.org/
Source:
https://git.sigsum.org/
Pads:
https://pad.sigsum.org/
Email:
https://lists.sigsum.org/
IRC: #sigsum @
OFTC.net
Matrix: #sigsum:matrix.org Jitsi:
https://meet.sigsum.org/
About Sigsum --- Sigsum started out as one part of the System Transparency project [6]. Early drafts of the public log element can be traced back to 2019 [7]. More focused design iterations started in October, 2020 [8]. Mature drafts of what is now sigsum logging was presented in Q2 of 2021 [9-11]. Links --- 1:
https://wiki.mozilla.org/Security/Binary_Transparency
2:
https://git.sigsum.org/sigsum/tree/doc/design.md
3:
https://git.sigsum.org/sigsum/tree/doc/api.md
4:
https://git.sigsum.org/sigsum-log-go/tree/README.md
5:
https://git.sigsum.org/sigsum/tree/archive
6:
https://git.sigsum.org/sigsum/tree/doc/history.md
7:
https://mullvad.net/blog/2019/6/3/system-transparency-future/
8:
https://github.com/system-transparency/stfe/commit/40250377da81864e9e502b80…
9:
https://web.archive.org/web/20210427203606/https://hopin.com/events/padsec
10:
https://web.archive.org/web/20210603112144/https://swits.hotell.kau.se/Annu…
11:
https://web.archive.org/web/20210923134324/https://swits.hotell.kau.se/Annu…
1 year, 7 months
1
0
0
0
← Newer
1
Older →
Jump to page:
1
Results per page:
10
25
50
100
200