The Sigsum team is happy to release a new version of the log-go log server software, version tag v0.16.0, succeeding the previous release v0.15.2. The source code for the release can be checked out from the git repository as git clone -b v0.16.0 https://git.glasklar.is/sigsum/core/log-go.git or installed using go install sigsum.org/log-go/cmd/...@v0.16.0 This release of the Sigsum log server fixes a log-poisoning issue, and overhauls the available metrics. See NEWS file for more details on changes, excerpt below. If you find any bugs, please report them on the sigsum-general@lists.sigsum.org mailing list or open an issue on GitLab in the log-go repository: https://git.glasklar.is/sigsum/core/log-go/ The expectations and intended use of the log server software is documented in the log-go RELEASES file. You will also find more information about the overall release process there, see https://git.glasklar.is/sigsum/core/log-go/-/blob/main/RELEASES.md. / The Sigsum team NEWS for log-go v0.16.0 This release of the Sigsum log server fixes a log-poisoning issue, and overhauls the available metrics. This release has been tested to work together with: * Sigsum tools (most importantly sigsum-submit and sigsum-verify, as well as sigsum-witness) https://git.glasklar.is/sigsum/core/sigsum-go, tags v1.0.0 as well as v0.14.1. Security improvement: * The log server now rejects add-leaf request where the submitter's public key is of low-order. This makes log-poisoning harder, since with a low-order key it's easy to generate a signature with 32 arbitrary chosen bytes in the signature. Incompatible changes: * Requires go-1.27 or later. * Extended and reworked prometheus metrics. See doc/metrics.md for available metrics. Miscellaneous: * Reduced the default publishing interval from 30s to 10s.
participants (1)
-
Niels Möller