> However, a CT log failure earlier this year due to MariaDB corruption after disk space exhaustion provided the motivation for a change. PostgreSQL, with its robust Write-ahead Logging (WAL) and strict adherence to ACID (Atomicity, Consistency, Isolation, Durability) principles, made it a better option for avoiding corruption and improving data integrity of the log.
This sounds incredibly suspicious to me. I wonder which storage engine they were using or if there was any unusual configuration that contributed to this issue.
chatmasta|1 year ago
Steampipe also has a crt.sh connector: https://hub.steampipe.io/plugins/turbot/crtsh/tables/crtsh_c...
politelemon|1 year ago
Better would be: CTL can now use a postgres backend.
bawolff|1 year ago
This sounds incredibly suspicious to me. I wonder which storage engine they were using or if there was any unusual configuration that contributed to this issue.
remram|1 year ago
unknown|1 year ago
[deleted]
nijave|1 year ago
dboreham|1 year ago
phoronixrly|1 year ago
westurner|1 year ago
Sigstore Rekor also has centralized Merkle hashes.
sluongng|1 year ago