Roughtime
Imperial Violet
SEPTEMBER 18, 2016
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. Even when the local clock is being synchronised, it's very likely to be using unauthenticated NTP.
Let's personalize your content