You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RTG-3686: Add WASM-compatible SCT validation with Chrome CT policy support
Adds sct_validator crate for validating Signed Certificate Timestamps (SCTs)
embedded in X.509 certificates, targeting WASM environments.
Key features:
- Chrome CT policy compliance (2-3 logs based on cert lifetime, 2 operators)
- ECDSA P-256 and RSA signature verification
- CT log list parsing from Google's JSON format
- Stale log list handling (auto-succeed after 70 days per Chrome policy)
Integration:
- New cron job fetches CT log list from Google
- Frontend validates SCTs when enable_sct_validation=true
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: crates/mtc_worker/config.schema.json
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -99,6 +99,11 @@
99
99
"minimum": 1,
100
100
"default": 60,
101
101
"description": "How long to wait in between runs of the partial tile cleaner."
102
+
},
103
+
"enable_sct_validation": {
104
+
"type": "boolean",
105
+
"default": false,
106
+
"description": "Enable SCT (Signed Certificate Timestamp) validation for bootstrap certificates. When enabled, submitted certificates must have valid embedded SCTs compliant with Chrome's CT policy."
0 commit comments