Adam Langley personal blog
Roughtime: a protocol for secure, auditable time synchronisation
Security protocols often assume an accurate, local clock (e.g. TLS, Kerberos, DNSSEC and more). It's a widely accepted assumption when designing protocols but, for a lot of people, it just isn't true. We find good evidence that at least 25% of all certificate errors in Chrome are due to a bad local clock.
- Points
- 120
- HN comments
- 16
- Submissions
- 1
- Cited by
- 3 commenters
Security & PrivacyNetworking & Internet2016
On Hacker News
| Submitted | Title on HN | Points | Comments |
|---|---|---|---|
| Sep 20, 2016 | Roughtime: a protocol for secure, auditable time synchronisation by bruo | 120 | 16 |
Cited in comments
Linked from 4 Hacker News comments by 3 different people, from Nov 2016 to May 2025.
Most recent:
- yencabulator · May 8, 2025
- yencabulator · Feb 2, 2025
- dsacco · Feb 6, 2018
- hannob · Nov 29, 2016
