Announcing Changes To Mammoth

824 views
Skip to first unread message

David Colon

unread,
Jan 13, 2023, 4:05:25 PM1/13/23
to Certificate Transparency Policy
Hello everyone,

Due to the stability issues with Mammoth over the past few months, we have been asked by Google's Chrome team for this log to stop accepting certificate submissions as soon as possible.  We plan on accomplishing this on or after 6PM EST (23:00 UTC) today.  We will keep everyone informed in this thread here on our progress to comply.

In addition to the above, we are actively working on migrating our test CT Log (Dodo) from "SuperDuper" to a Trillian based architecture.  Upon success, we plan on updating the public about our plans for Sabre.  Furthermore, we plan on standing up temporal sharded logs in the near future to  continue our involvement in the CT ecosystem.

Ryan Hurst

unread,
Jan 13, 2023, 5:22:22 PM1/13/23
to Certificate Transparency Policy, David Colon
David,

Thank you for the update and thanks to everyone at Sectigo for their continued support of the CT ecosystem!

Ryan Hurst

David Colon

unread,
Jan 13, 2023, 9:57:26 PM1/13/23
to Certificate Transparency Policy, Ryan Hurst, David Colon
Hello all,

Mammoth will no longer accept new certificate submissions.  We made the changes around 8:20PM EST (01:20 UTC).  We expect Mammoth to be running ~15 hours after aforementioned time.  The 15 hours is the last known time to start from boot.

Best,
David

David Colon

unread,
Jan 13, 2023, 10:23:06 PM1/13/23
to Certificate Transparency Policy, David Colon, Ryan Hurst
Hello all,

Our migration of our CT Test Log (Dodo) from SuperDuper to Trillian hit a snag.  We will continue working on it Monday.  If we continue to hit problems, we plan on reaching out to the Trillian dev team for assistance.

Best,
David

Pierre Phaneuf

unread,
Jan 16, 2023, 4:43:24 AM1/16/23
to David Colon, Certificate Transparency Policy
Thanks for the update, and well done to the Sectigo team for running what I believe might be the largest fully open source CT log, for quite some time! For all the trouble it's given you, SuperDuper was only designed for about 100M entries (the Google logs were the largest by a stretch, and weren't even 10M at the time), and you've taken it well on its way to 10x that, very impressive work!

We'll do our best to assist you with these migrations.

--
You received this message because you are subscribed to the Google Groups "Certificate Transparency Policy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ct-policy+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/ct-policy/c1baf809-233a-4acd-9bc9-f06f2d17125bn%40chromium.org.

David Colon

unread,
Jan 21, 2023, 12:19:30 PM1/21/23
to Certificate Transparency Policy, Pierre Phaneuf, Certificate Transparency Policy, David Colon
Thanks Pierre, we appreciate the kind words and support here at Sectigo CT Ops.

All,

Below are some updates:
  • As previously mentioned, mammoth.ct.comodo.com no longer accepts certificate submission as of 2023/01/14 01:20 UTC
  • mammoth.ct.comodo.com came back online at 2023-01-14 15:18:13 - finished the last SCTs and has not changed it's STH since.  We've experienced 100% uptime since.
  • dodo.ct.comodo.com was migrated over to Trillian on Thursday, 2022/01/19
  • We stood up a new Trillian log for Sabre and started to mirror certificates from SuperDuper implementation to Trillian.  We hit a snag with our disk space estimation and stopped migration.  We plan on resuming again Monday.  Based on our current estimates, it will take 4.5 days to have the Trillian log implementation caught up.  We plan on reaching out to the Trillian dev team to make sure our migration approach is correct.  Once verified, we plan on announcing the switch to Trillian in a new thread here
Best,
David
Reply all
Reply to author
Forward
0 new messages