Re:New attacks on Network Time Protocol can defeat HTTPS and...
by PhantomGremlin on Friday October 23, 2015 @04:03AM
(#10437387)
OpenNTPD has implemented a clever mitigation to this problem. It relies on trusting various key sites such as Google. You put one or more lines like this into your configuration file:
As the man page puts it:
Of course, the devil is in the details. IIRC at the moment this check is only made when NTPD starts up, and not periodically during operation. But the general idea is probably quite solid.
[ Parent
| on HN ]
Re:New attacks on Network Time Protocol can defeat HTTPS and...
by mlichvar on Friday October 23, 2015 @10:46AM
(#10438879)
The problem with this solution is that it's very expensive. Imagine couple hundreds of millions of computers making a TLS connection every few minutes.
For NTP there is Autokey (RFC 5906), which allows authentication of the servers with public-key crypto. It has various problems, one of them is that it's insecure.
The NTP working group is currently preparing a Network Time Security specification and its implementation in NTP, which is supposed to replace Autokey.