From 5ba4a77233549819440cc41a02503f3a85213e24 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Sat, 18 Dec 2021 18:44:56 +0100 Subject: issues: Fix error-prone timestamp configuration --- issues/fix-error-prone-timestamp-configuration.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create 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 new file mode 100644 index 0000000..79db548 --- /dev/null +++ b/issues/fix-error-prone-timestamp-configuration.md @@ -0,0 +1,23 @@ +**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