From 0b0320d8f295394e2afc5f0cf012422e8625518b Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Mon, 27 Sep 2021 22:06:31 +0200 Subject: imported issues --- issues/add-read-only-mode.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 issues/add-read-only-mode.md (limited to 'issues/add-read-only-mode.md') diff --git a/issues/add-read-only-mode.md b/issues/add-read-only-mode.md new file mode 100644 index 0000000..d87c244 --- /dev/null +++ b/issues/add-read-only-mode.md @@ -0,0 +1,14 @@ +# Add read-only mode +Reported by: rgdd + +The process of shutting down a log will likely consist of at least two steps: +1. Stop accepting new logging requests. Serve the final (co)signed tree heads +for a while. +2. Take the log offline. + +The first step requires some form of read-only mode. For example: +- Disable all write endpoints (`add-leaf` and `add-cosignature`) +- Implement a `StateManager` that serves fixed (co)signed tree heads. + +For inspiration we could look at certificate transparency: +- https://github.com/google/certificate-transparency-go/tree/master/trillian/ctfe -- cgit v1.2.3