Commenters describe Merkle Tree certificates as a new X.509 design that combines certificate issuance with public logging in the style of Certificate Transparency. One commenter says the integration could reduce logging overhead as certificates become shorter-lived and post-quantum cryptography brings much larger signatures; an optional optimization can avoid signatures for up-to-date relying parties and older certificates. Some welcome the use of Merkle trees, while another asks whether the system is essentially a centralized blockchain. A commenter clarifies that ACME, the protocol used to request certificates, is separate from the certificate format.
A central point of debate is the operational impact of shorter certificate lifetimes. Commenters argue that frequent renewal can reduce reliance on OCSP and CRLs, making certificates expire quickly enough that waiting replaces much of the need for revocation. One warns that MTCs may be limited to seven-day certificates, ACME issuance, and eventual Chrome support requirements, urging site operators to automate renewals. Another corrects the Chrome figure: its stated maximum is 47 days, while Apple has announced a seven-day limit but has not yet published a draft policy. Despite differing figures and expectations about adoption, commenters broadly endorse automating certificate management and see short lifetimes as beneficial, even if they overturn the old assumption that certificates should last years.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.