RTC's are plenty accurate nowadays so you shouldn't need to check for time updates very often, so if you make ntpd run at boot then once a week using the -q flag (this makes ntpd check, update then exit) then the NTP attack vector takes a very long time to execute.
Ntpd by default will error when the returned time from an NTP server differs against the system clock by more than 1000s. many ARM boards), it's not so great in situations when time synchronisation is an attack vector. Timesyncd is by default designed to accept ANY time response and adjust the system clock, while this is great for desktops or systems with no RTC (e.g. One thing that all these howto's miss is if you're running Ubuntu you really need to replace timesyncd with ntpd.
0 kommentar(er)
