From: jack@handsome.com   
      
   The other day I was unable to log in to one of my financial accounts. Took   
   several days to work out what the problem was, but now it seems that my   
   computer clock was several minutes wrong. The web site requires you to use   
   an authenticator app, and my app was generating the wrong codes from the   
   system clock.   
      
   Why was the clock wrong? The GUI Time and Date Settings utility had "Keep   
   synchronised with Internet servers" selected, though it didn't provide a   
   way of choosing an NTP. You'd have thought this meant it would go to a   
   default server, but it obviously hadn't.   
      
   Turns out that my version of LM doesn't come with the service that keeps   
   the clock synced to an NTP server.   
      
   I did some research and found that LM's utility (or setting, whatever you   
   call it) for doing this is systemd-timesyncd.service. But it had either   
   never been installed, or was masked, or had not been set to start up, and   
   nowhere is there a prompt telling users to do this. Nor am I the first   
   person to be troubled by this.   
      
   WTF?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)