News for hackers. Stuff that matters.
Re:Excessive load on NTP servers by CaptSpify on Tuesday December 20, 2016 @11:25AM (#13221240)
Stupid decision by SC for sure, but is there a reason there is no rate-limiting on the NTP servers? I'm not up to date on their structure. Maybe it's just not feasible because they don't synchronize clients?
Re:Excessive load on NTP servers by devicenull on Tuesday December 20, 2016 @11:45AM (#13221461)
The NTP servers are all run by random members of the community. There's no real coordination between them (outside of being part of the pool), so you can't really rate limit between servers.

The library was only doing a couple request per NTP server, so rate limiting really wouldn't have helped.

Re:Excessive load on NTP servers by dfox on Tuesday December 20, 2016 @11:38AM (#13221380)
Even without thinking about storing some context, replying to NTP request is probably similarly expensive as evaluating whether it should be rate limited.
Re:Excessive load on NTP servers by coderholic on Tuesday December 20, 2016 @01:11PM (#13222338)
Yeah exactly this. Rate limiting isn't free. It's almost certainly more expensive to rate limit than to statelessly respond with the time.
Re:Excessive load on NTP servers by paulgear on Tuesday December 20, 2016 @01:52PM (#13222731)
NTP does store context for a limited number of clients (600 by default). https://www.eecis.udel.edu/~mills/ntp/html/miscopt.html
Re:Excessive load on NTP servers by takeda on Tuesday December 20, 2016 @02:12PM (#13222921)
Rate limiting can only control number of responses issued by the server, it won't help reduce number of incoming UDP requests.

NTP has KOD (Kiss of Death) which was meant for that situation, but it is often ignored/not handled properly by applications :/

Re:Excessive load on NTP servers by paulgear on Tuesday December 20, 2016 @01:33PM (#13222540)
NTP has rate limiting built into the protocol (https://www.eecis.udel.edu/~mills/ntp/html/accopt.html), but Snapchat appear to be using a large list of servers.

Also, NTP runs on UDP rather than TCP, and it only requires one packet from each party to exchange time, so it's harder to rate-limit it without making your server unreliable.