Attributed metadata history
Up to 100 retained publisher events per page for ab2d37410b3ea10fae63854783ab0ecfd49d70de81f6c4ab2184acd63fe1e79b. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
available
Fingerprint: 3ee9ede72037d42a31a54231e2db3aca2f948cab8548bb5974fefbf1d8cf8232
intelligence_src_823f7b237762257237
observed · 2026-10-12 12:09:04 UTC
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. 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 Our Oak log is the only qualified CT log that runs on an entirely open source stack 3. 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: The disk I/O workload of Trillian atop MariaDB is easily mediated by front-end rate limits, and It’s worth the complexity to split each new annual CT log into its own Trillian/MariaDB stack. This post will update some of the information from the previous post How Let’s Encrypt Runs CT Logs. Growing Oak While Staying Open Source Oak runs on a free and open source stack: Google’s Trillian data store, backed by MariaDB, running at Am
Fingerprint: 324d3712d1c90a71a1a7e60735c22cb222829167e4714b38a8d3194781739131