Re:Multiple vulnerabilities released in NTP
by xorcist on Saturday December 20, 2014 @02:33AM
(#8776088)
For that to work you need to compromise _all_ the NTP servers those servers sync to for an extended period of time (years). It's simply not a realistic attack.
NTP does not sync time. NTP measures time drift across groups of servers, and sprinkles in known time. I'm not saying authentication is useless, you should turn it on for your known time sources, but it's not so simple as you make it out to be.
Unless you use SNTP on your servers. Don't do that. Ever.
Re:Multiple vulnerabilities released in NTP
by agwa on Saturday December 20, 2014 @10:45AM
(#8776873)
In practice, there are systems that use SNTP or regular NTP with periodic calls to ntpdate. Ubuntu does the latter, by default, and is thus susceptible to the attacks I described,
Re:Multiple vulnerabilities released in NTP
by xorcist on Sunday December 21, 2014 @03:36AM
(#8779294)
That's a bug with Ubuntu. That mode of operation is for devices without persistent real time clocks or personal laptops where time isn't that important. If you sync your time at reboots you will screw up ntpd's clock drift calculations.
Re:Multiple vulnerabilities released in NTP
by tedunangst on Friday December 19, 2014 @03:32PM
(#8774339)
Pretty persistent attacker. It should take something like 100 days to push the clock off by one day.
Re:Multiple vulnerabilities released in NTP
by hannob on Friday December 19, 2014 @03:44PM
(#8774400)
Ubuntu accepts arbitrary time jumps, the attack was presented live at BH with an Ubuntu System.
You could also cause expired certificates to be accepted, which limits the utility of short-lived certs as a means of protecting against key compromise.
And as hannob said, you can circumvent HSTS by setting the time in the future, causing all HSTS entries to be expired.