#TRILLIAN FOR WEB UPDATE#

Other operators of Trillian have opted to use different databases which segment data differently, but the provided MySQL-compatible datastore has successfully kept up with Let’s Encrypt’s CT log volume (currently above 400 GB per month). To our knowledge, Oak is the only trusted CT log without closed-source components 3. Oak runs on a free and open source stack: Google’s Trillian data store, backed by MariaDB, running at Amazon Web Services (AWS) via Amazon’s Relational Database Service (RDS).

#TRILLIAN FOR WEB UPDATE#

This post will update some of the information from the previous post How Let’s Encrypt Runs CT Logs. It’s worth the complexity to split each new annual CT log into its own Trillian/MariaDB stack. The disk I/O workload of Trillian atop MariaDB is easily mediated by front-end rate limits, and

In the interest of lowering the barrier for other organizations to join the CT ecosystem, we want to cover a few recent changes to Oak that might be helpful to anyone else planning to launch a log based on Google’s Trillian backed by MariaDB: Our Oak log is the only qualified CT log that runs on an entirely open source stack 3. CT logs have become important infrastructure for an encrypted Web 1, but have a well-deserved reputation for being difficult to operate at high levels of trust: Only 6 organizations run logs that are currently considered to be “qualified.” 2 Let’s Encrypt has been running a Certificate Transparency (CT) log since 2019 as part of our commitment to keeping the Web PKI ecosystem healthy. Nurturing Continued Growth of Our Oak CT Log

Trillian for web