Skip to content
NewA calmer, faster ZeroHour

Accountability in Certificate Transparency and Variants

arXiv cs.CRby Timo Treitz ()1 min read4 · 4 reads
AI summary · glm-5.3-flashSummaries by Vani AI

Formal Dolev-Yao analysis shows plain Certificate Transparency requires an honest log, SCT Auditing removes that assumption, and Gossiping does not.

The paper analyzes accountability in Certificate Transparency and its SCT Auditing and Gossiping extensions in the Dolev-Yao model, starting from a vanilla PKI. It finds plain CT provides accountability only under the assumption of an honest log. The SCT Auditing extension can eliminate that assumption, while the Gossiping extension cannot. CT is supported by all major browsers and obliges Certificate Authorities to record issued certificates in public, monitored logs.

Key facts
  • Plain CT provides accountability only if the log is honest
  • SCT Auditing extension removes the honest-log assumption; Gossiping does not
  • Analysis spans vanilla PKI through CT variants in the Dolev-Yao model
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

1 min read at arxiv.org

Certificate Transparency (CT) aims to reduce the trust required in Certificate Authorities (CAs) within the TLS certificate ecosystem. It is supported by all major browsers. The protocol obliges all CAs to record the certificates they issue in a public log, which itself is monitored for compliance and consistency by third parties.

arXiv cs.CR

By Timo Treitz · arxiv.org

Read the full article at arXiv cs.CR

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.