Re:Multiple vulnerabilities released in NTP
by mbq on Friday December 19, 2014 @01:53PM
(#8773787)
There is also systemd-timesyncd and Chrony.
[ Parent
| on HN ]
Re:Multiple vulnerabilities released in NTP
by TD-Linux on Friday December 19, 2014 @02:21PM
(#8773953)
Fedora (or GNOME 3?) uses Chrony by default due to better power management. I assume the same is true for most other distributions.
systemd-timesyncd is not much of an alternative. It is simply an sntp client, it does not serve time to other hosts nor can it use reference clocks.
Sure, but IMO enough many systems use NTP only in a sntp manner to mention it.
Re:Multiple vulnerabilities released in NTP
by _wmd on Saturday December 20, 2014 @12:52AM
(#8775970)
SNTP is only useful as an option of last resort, e.g. you have no embedded RTC, and no storage to track drift. In all other cases a full NTP client is always preferable, since drift and corrections can be applied without causing jumps to the system clock (triggering software bugs and misfired events), and drift statistics can be recorded -- which is inevitably required in almost all circumstances where you're using even high end PC motherboards that still rely on a $.15 crystal time reference
Re:Multiple vulnerabilities released in NTP
by xorcist on Saturday December 20, 2014 @02:21AM
(#8776075)
SNTP is close to useless. Your time server could be off and you'd happily follow along.
Re:Multiple vulnerabilities released in NTP
by vezzy-fnord on Friday December 19, 2014 @02:34PM
(#8774019)
systemd-timesyncd implements SNTP, which is not the same.