Aviator Freeze - process starts today 2016-11-29

[Paul Hadfield]

Hi CT afficionados,

per the Chrome CT policy decision, Google's Aviator log must be in a frozen state at 2016-12-01T00:00:00Z.

The process that gets it to that state starts today. Here's an overview of the timetable:

1. at around 2016-11-29 12:00:00 UTC, Aviator will switch to read-only mode.  The /ct/v1/add{-pre}-chain API endpoints will no longer be available for use.

2. Aviator will continue signing its tree for a further 24 hours, allowing a full MMD to pass from the last SCT it issues before it going read-only

3. at around 2016-11-30 12:00:00 UTC, Aviator's signing process will be permanently suspended.

4. Google will then announce the final STH.

The log's get-* APIs will continue to be functional throughout this process, and thereafter until further notice.

regards,

Paul

[Paul Hadfield]

On Tue, Nov 29, 2016 at 10:03 AM, Paul Hadfield <hadf...@google.com> wrote:

Hi CT afficionados,

per the Chrome CT policy decision, Google's Aviator log must be in a frozen state at 2016-12-01T00:00:00Z.

The process that gets it to that state starts today. Here's an overview of the timetable:

1. at around 2016-11-29 12:00:00 UTC, Aviator will switch to read-only mode.  The /ct/v1/add{-pre}-chain API endpoints will no longer be available for use.

2. Aviator will continue signing its tree for a further 24 hours, allowing a full MMD to pass from the last SCT it issues before it going read-only

3. at around 2016-11-30 12:00:00 UTC, Aviator's signing process will be permanently suspended.

4. Google will then announce the final STH.

The freeze of Aviator is now complete.  Please see https://bugs.chromium.org/p/chromium/issues/detail?id=389514 for further details.

regards,

Paul