From 601d2ee04840d24fe13e5ec54ae09f2a623f3d02 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Tue, 28 Dec 2021 21:32:38 +0100 Subject: db: Fix error prone timestamp configuration The timestamp for the latest tree head is now set based on the current UNIX time. This means that there is no longer any reliance on Trillian to move the timestamp forward every 5 minutes, just set -interval=300s. --- issues/fix-error-prone-timestamp-configuration.md | 23 ----------------------- 1 file changed, 23 deletions(-) delete mode 100644 issues/fix-error-prone-timestamp-configuration.md (limited to 'issues') diff --git a/issues/fix-error-prone-timestamp-configuration.md b/issues/fix-error-prone-timestamp-configuration.md deleted file mode 100644 index 79db548..0000000 --- a/issues/fix-error-prone-timestamp-configuration.md +++ /dev/null @@ -1,23 +0,0 @@ -**Title:** Fix error-prone timestamp configuration
-**Date:** 2021-12-18
- -# Summary -Stop relying on Trillian to update tree head timestamps. - -# Description -A sigsum log is expected to produce a new to-sign tree head every five minutes. -If no new entries were added, only the timestamp is updated to ensure freshness. - -The current sigsum-log-go implementation assumes that Trillian ensures that a -new tree head is produced every five minutes. It can be configured as follows: -``` -$ createtree --help -Usage of ./createtree: -[...] - -max_root_duration duration - Interval after which a new signed root is produced despite no submissions; zero means never (default 1h0m0s) -[...] -``` - -It would be less error-prone to configure this from sigsum-log-go instead, as -part of the `StateManager` interface based on a constant (i.e., 5 minutes). -- cgit v1.2.3