The Sigsum team is happy to release a new version of the log-go log server software, version tag v0.15.2, succeeding the previous release v0.15.0. The source code for the release can be checked out from the git repository as

git clone -b v0.15.2 https://git.glasklar.is/sigsum/core/log-go.git

or installed using

go install sigsum.org/log-go/cmd/...@v0.15.2

This is a bugfix release. The most important change is a correction to how the log server applies its configured rate limits. See NEWS file for 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.15.2

This is minor release fixing a few issues found since the previous release. Upgrading from the previous release is expected to work with no issues.

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, tag v0.11.2.

Improvements:

* Fixed a bug in the rate-limit logic. The intended behavior is to only count the first add-leaf requests for a particular leaf, and not count retries for the same leaf. In v0.15.0, retries could exhaust the rate limit quota.

* More relevant logging of witness errors. When a witness starts failing, and when it recovers, the error is logged at INFO level. Repeated errors are logged at DEBUG level. In v0.15.0, all errors were logged at DEBUG level, i.e., no errors logged by default.

Incompatible changes:

* The --max-range command-line option is now only available for the primary node. Before this change, there was a --max-range command-line option also for the secondary node but that option had no effect.

Miscellaneous:

* Increased max-range default value to 512.

* Updated config.toml.example file and added a corresponding test to help ensure the example config stays up-to-date.