3 ms·
What's really fun is when you use a custom time protocol over TLS, but the host's clock is so far gone that the TLS cert is not valid. D'oh!
by drewg123 3y ago
What's really fun is when you use a custom time protocol over TLS, but the host's clock is so far gone that the TLS cert is not valid. D'oh!
- j16sdiz 3y agoThat's what you got for NTP using domain name, with DNS over HTTPS.
- rajnathani 3y agoWe noticed this in our custom embedded Linux device (at work), where when we didn't have the time sync with NTP turned on for boot (but rather a cron job at an interval further away from boot time) and that our RTC's coin cell was drained due to a small hardware bug, that at first when our API calls from the device were failing that we thought it was a hardware / software driver (WLAN) issue, but it fortunately turned out to be the innocuous issue of TLS failing due to the system clock being so off!