11–20 of 34 posts
The most common embedded NTP implementation is probably busybox, being used on Linux routers/modems/etc.. is actually based on OpenNTPD.
why dont dns servers provide this capability? seems like they are the most centralized of all the online services.
it doesn't take 30 years to create a time sync protocol. it doesn't take 100 days to fix a malformed packet issue.
these are lazy money grubbers who take more time to rant about how no one gives them free money to fix mistakes they made themselves while being paid.
take responsibility. stop whining.
you're all idiots.
Article doesn't bother to mention that there are completely different projects which implement NTP servers with varying levels of functionality (openntpd, chrony, ntpsec, ntimed). And while the pool.ntp.org system is a nice scheme, it's hardly a global necessity. You can fairly easily get a stratum 1 server going on your own infrastructure. IMHO, too much of NTP relies on GPS, but that's a separate matter.
Article doesn't bother to mention that there are completely different projects which implement NTP servers with varying levels of functionality (openntpd, chrony, ntpsec, ntimed). And while the pool.ntp.org system is a nice scheme, it's hardly a global necessity. You can fairly easily get a stratum 1 server going on your own infrastructure. IMHO, too much of NTP relies on GPS, but that's a separate matter.
I'm curious to know more. Can you please elaborate or point to some articles discussing this?
Article doesn't bother to mention that there are completely different projects which implement NTP servers with varying levels of functionality (openntpd, chrony, ntpsec, ntimed). And while the pool.ntp.org system is a nice scheme, it's hardly a global necessity. You can fairly easily get a stratum 1 server going on your own infrastructure. IMHO, too much of NTP relies on GPS, but that's a separate matter.
> IMHO, too much of NTP relies on GPS, but that's a separate matter. I'm curious to know more. Can you please elaborate or point to some articles discussing this?
http://www.ntp.org/ntpfaq/NTP-s-refclk.htm
TL;DR Most NTP networks are relying on GPS versus a high precision on-site time keeping device. Break GPS, and you break timekeeping for a wide swath of the worldwide NTP pool. But thems the breaks when you can get access to atomic clocks in space (each GPS satellite carries an atomic clock on board) just by sticking an antenna out the window.
If you require precision time for critical business operations (financial transactions, global database operations), you should be running a precision time source locally at your datacenter; for under $20 an attacker could deny you GPS timing.
I thought NTP was a protocol, not a piece of software. Is the article conflating them, or is there only one single implementation of it that everyone relies upon?
While the implementation is popular, there are alternatives. There is also OpenNTPd, chrony and ntimed for instance.
There are also alternatives to the NTP protocol too, such as PTP and SNTP.
[1]https://www.ietf.org/rfc/rfc5905.txt [2]http://www.ntp.org/
Classic NTP is hardly the only game in town. For example, see the NTPsec work in progress: https://www.ntpsec.org/ which I'll probably transition to someday, maybe even get an el-cheapo GPS receiver now that I'm not effectively living in a basement. And I've personally be using chrony for a while, although my needs are significantly less than whatever level of accuracy it provides. There are some other clients out th…
It was discovered a while ago for example that some part of the Linux default NTP servers are run by shodan. So when your machine gets the time it lets shodan know you've got a server running so they can port scan you.
It would be stupid not to run a bunch of NTP servers if you wanted a to run a bot net. A free list of every running Linux server and countless IoT devices! Without having to actively scan IP space at all
Earlier quoted context omitted.
> IMHO, too much of NTP relies on GPS, but that's a separate matter. I'm curious to know more. Can you please elaborate or point to some articles discussing this?
https://ntpserver.wordpress.com/2008/09/10/ntp-server-stratu... http://www.ntp.org/ntpfaq/NTP-s-refclk.htm TL;DR Most NTP networks are relying on GPS versus a high precision on-site time keeping device. Break GPS, and you break timekeeping for a wide swath of the worldwide NTP pool. But thems the breaks when you can get access to atomic clocks in space (each GPS satellite carries an atomic clock on board) just by sti…
Especially when using distributed databases where write priority is determined by timestamp, someone wrecking havoc with your time source could bring down the database