Roughtime: Securing Time with Digital Signatures
When you visit a secure website, it offers you a TLS certificate that asserts its identity. Every certificate has an expiration date, and when it’s passed due, it is no longer valid.
When you visit a secure website, it offers you a TLS certificate that asserts its identity. Every certificate has an expiration date, and when it’s passed due, it is no longer valid. The idea is almost as old as the web itself: limiting the lifetime of certificates is meant to reduce the risk in case a TLS server’s secret key is compromised. Certificates aren’t the only cryptographic artifacts that expire. When you visit a site protected by Cloudflare, we also tell you whether its certificate has been revoked (see our blog post on OCSP stapling) — for example, due to the secret key being…
saved by
related reading
- A Post-Quantum Future for Let's Encrypt - Let's Encryptletsencrypt.org
- Keeping the Internet fast and secure- introducing Merkle Tree Certificatesblog.cloudflare.com
- Timeful (formerly Schej) - Find a time to meetschej.it
- TLS fingerprinting: How it works, where it is used and how to control your signature | lwt hikerlwthiker.com
- Tyblog | You Don't Love systemd Timers Enoughblog.tjll.net
- LN 039: Notes on timealexanderobenauer.com
- DNSSEC | Computer Securitytextbook.cs161.org
- ActivityWatch - Open-source time trackeractivitywatch.net
- Python time.time() vs time.perf_counter() – SuperFastPythonsuperfastpython.com
- thesis.pdfaayushg.com
- timed commitmentsiacr.org
- Temporal Primer - Building Long-Running Systemsarpitbhayani.me