4 ms·
It's simpler than that. Knowingly hardcoding someone else's timeservers without even speaking with the operator of said timeservers is Internet hostility, parti
by jsmthrowaway 11y ago
It's simpler than that. Knowingly hardcoding someone else's timeservers without even speaking with the operator of said timeservers is Internet hostility, particularly when your project is popular enough to be deployed on potentially millions of machines. D-Link hardcoded PHK's timeserver many years ago:
https://people.freebsd.org/~phk/dlink/ https://people.freebsd.org/~phk/dlink/
Netgear hardcoded the University of Wisconsin even earlier than that:
http://pages.cs.wisc.edu/~plonka/netgear-sntp/ http://pages.cs.wisc.edu/~plonka/netgear-sntp/
The best part about the Netgear one was it hit upwards of a quarter million packets per second and actively resisted mitigation by admins. Seriously, don't hardcode. Ever.
- deleted 11y ago[deleted]
- scrollaway 11y agoCompanies won't learn until the time servers they shipped on hundreds of thousands of products stop working from one day to the next because the operator of the server didn't feel like offering them a free service.
- digi_owl 11y agoI seem to recall reading about a French made program that had hardcoded the Linux source FTP server. Apparently it was used as part of a bandwidth test. And it got so popular that the server admins had to ban the French IP range...