News for hackers. Stuff that matters.
Re:Multiple vulnerabilities released in NTP by imanaccount247 on Friday December 19, 2014 @04:04PM (#8774503)
>nor do they have all of the required algorithms required for proper timekeeping.

I hear something like that a lot, yet all my systems run openntpd and all of them are keeping proper time without issue. What exactly is so not proper about it, and which algorithm exactly does it need to be "proper"?

Re:Multiple vulnerabilities released in NTP by tedunangst on Friday December 19, 2014 @05:51PM (#8775020)
People who are into timekeeping are like, really, really into timekeeping. I've been skating by with improper timekeeping, too (whatever that means), but I only need to correlate web log entries and not hadron collisions.
Re:Multiple vulnerabilities released in NTP by noselasd on Friday December 19, 2014 @09:25PM (#8775651)
I do not know if this is an issue with other ntp daemons today, but I've been bitten by some of them in the distant past - they might keep the time fine, but it really sucks if they sometimes jump the clock instead of properly slewing it.

Having to try to debug intricate problems and not knowing if you can trust timestamps on the logs for the actual order of events can drive you nuts.

Re:Multiple vulnerabilities released in NTP by wglb on Friday December 19, 2014 @08:44PM (#8775554)
From the openntpd.org site at http://www.openntpd.org/goals.html:

Reach a reasonable accuracy. We are not after the last microseconds.

Whereas NTP looks for maximum accuracy.

Re:Multiple vulnerabilities released in NTP by imanaccount247 on Friday December 19, 2014 @10:24PM (#8775775)
There's a big difference between "proper" and "more accurate than 99.999999999% of people care about" though. How many microseconds of accuracy do most people need? How many does openntpd provide and how many does the other ntpd provide? Claiming it isn't "proper" because in theory it may be 2 microseconds less accurate in some circumstances sounds like FUD.