From 461d447763059e4b76cc27ea2f1853897b609b9a Mon Sep 17 00:00:00 2001
From: Seirdy <seirdy@seirdy.one>
Date: Thu, 23 Jan 2025 00:02:14 -0500
Subject: [PATCH] new note: CT in Firefox

---
 content/notes/certificate-transparency-in-firefox.md | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 content/notes/certificate-transparency-in-firefox.md

diff --git a/content/notes/certificate-transparency-in-firefox.md b/content/notes/certificate-transparency-in-firefox.md
new file mode 100644
index 0000000..3bc30f8
--- /dev/null
+++ b/content/notes/certificate-transparency-in-firefox.md
@@ -0,0 +1,11 @@
+---
+title: "Certificate Transparency in Firefox"
+date: 2025-01-23T00:03:14-05:00
+draft: true
+---
+
+[Firefox 136 looks poised to enforce Certificate Transparency](https://bugzilla.mozilla.org/show_bug.cgi?id=1927085).
+
+It may be late, but combined with CRLite ([and its other Web PKI progress](https://seirdy.one/posts/2024/09/25/post-ocsp-revocation/#aside-browser-wars)), it seems to now be the browser with the most robust Web PKI support.
+
+While I would still say that Chromium generally wins on the security front, I'm happy to see the gap narrow with time and to see Firefox occasionally inch ahead in some areas.